2 goals actually:
- let people test it (you can say what you want excepted for few dev
while it is not on central it is not grabbed)
- let tomee use a release of jcs 2 instead of the snapshot it depends on
For that purpose (mainly first point) a beta is perfect
Romain Manni-Bucau
@rmannibucau
ht
It's still not clear to me what your goal is though as you did not answer
my question... ;-)
Gary
On Mon, Nov 17, 2014 at 12:32 PM, Romain Manni-Bucau
wrote:
> Well playing with SVN is fine a moment but some projects start to
> depend on SNAPSHOT and it can last forever (typically the case for
Well playing with SVN is fine a moment but some projects start to
depend on SNAPSHOT and it can last forever (typically the case for
TomEE since some weeks to not say more).
I'll cancel the vote today, not sure I'll be able to reroll it this
month so if anyone has some cycles and will of doing it
This vote is cancelled since procedure was not correct
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2014-11-17 18:32 GMT+01:00 Romain Manni-Bucau :
> Well playing with SVN is fine a moment but some projects start to
> d
I see several paths for you.
First, cancel the VOTE thread.
Second, decide if you want to tell people to grab the latest from SVN and
experiment or release an Alpha or Beta. If you want a release, go through
the process again...
Then publicize the availability of the code in SVN or a release to
Basically I just want to release to let people grap it but I don't
want to prevent some API changes (so not yet a 2.0). Switched to a RC1
cause of all these commons release links.
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibu
Let's step back here.
Do you want to release an Alpha or Beta? As opposed to a telling people to
try out what is in the HEAD of trunk?
If you do release 2.0, the implications are strict as to what API changes
are allowed WRT binary compatibility.
If so you can do that if the JCS community agrees
basically that's not what we (I maybe?) wanted to do. this was really
a RC (I even wanted to call it beta). So version is correct from this
point of view. I sadly didn't notice it was "conflicting" with commons
habits.
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wo
No, the release candidate tag and project version should not match exactly.
The tag is a release candidate. What we are voting to produce is version
2.0, so whatever the tag points to should build version 2.0, not 2.0-RC1,
not a snapshot, just 2.0. We can have any number of tags 2.0-RC1, 2, 3 and
s
@Gary: wdym? rc version is RC1 so it matches project version finally.
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2014-11-17 17:38 GMT+01:00 Gary Gregory :
> -1
>
> The files at the tag are incorrect, least the POM is
-1
The files at the tag are incorrect, least the POM is wrong:
https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.0-RC1/pom.xml
because the project version is 2.0-RC1 instead of 2.0.
I've not found one cannonical receipt for releasing out of commons sadly, I
use both
- https
On Sun, Nov 16, 2014 at 3:52 PM, Romain Manni-Bucau
wrote:
> Plugins means modules?
> http://people.apache.org/~rmannibucau/commons-jcs-2.0-RC1/modules.html
>
Yes, thank you, I keep on missing those...
Gary
>
> mvn site should worrk while folders are deployed as the project structure
> no?
>
Plugins means modules?
http://people.apache.org/~rmannibucau/commons-jcs-2.0-RC1/modules.html
mvn site should worrk while folders are deployed as the project structure
no?
Le 16 nov. 2014 21:37, "Gary Gregory" a écrit :
> Also, I still do not see links from the main site to the plugin sites whic
Also, I still do not see links from the main site to the plugin sites which
should have all their reports.
IOW, doing 'mvn site' is not going to work for a multi-module site. See
Log4j 2 for an example of a multi-module site build.
Gary
On Sun, Nov 16, 2014 at 3:11 PM, Gary Gregory
wrote:
> On
On Sun, Nov 16, 2014 at 12:55 PM, Romain Manni-Bucau
wrote:
> about the command: mvn site.
> about rat report: yeah both should be excluded (I'll update it just
> after this mail)
> about the historical note: I'll try to tackle it as well
>
Great, thanks.
Another thing that is a roadblock to ge
2014-11-16 18:55 GMT+01:00 Romain Manni-Bucau :
> about the command: mvn site.
> about rat report: yeah both should be excluded (I'll update it just
> after this mail)
weird it was:
org.apache.rat
apache-rat-plugin
.java-version
**/LIC
about the command: mvn site.
about rat report: yeah both should be excluded (I'll update it just
after this mail)
about the historical note: I'll try to tackle it as well
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
201
The release notes mention older versions of pre 2.0 JCS but the previous
versions are not available under the commons-jcs AID in Maven Central,
therefore a brief historical not would be helpful on the site IMO.
Gary
On Wed, Nov 12, 2014 at 4:23 AM, Romain Manni-Bucau
wrote:
> Hi
>
> I'm trying
The main RAT report on your site shows:
Unapproved licenses:
src/scripts/zipcodes.txt
LICENSE.xerox
So you need to exclude the LICENSE.xerox from the check I would guess.
Either add a license header to src/scripts/zipcodes.txt or exclude it,
not sure which is more appropriate.
I'm not sur
What maven command did you use to create the whole site?
Thank you,
Gary
On Wed, Nov 12, 2014 at 4:23 AM, Romain Manni-Bucau
wrote:
> Hi
>
> I'm trying to align on commons standards this time.
>
> - here is the maven repo:
> https://repository.apache.org/content/repositories/orgapachecommons-10
upated
http://people.apache.org/~rmannibucau/commons-jcs-2.0-RC1/JCSandJCACHE.html
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2014-11-15 10:59 GMT+01:00 Romain Manni-Bucau :
> 2014-11-14 18:24 GMT+01:00 Thomas Vandah
2014-11-14 18:24 GMT+01:00 Thomas Vandahl :
> On 12.11.14 10:23, Romain Manni-Bucau wrote:
>> Hi
>>
>> I'm trying to align on commons standards this time.
>>
>> - here is the maven repo:
>> https://repository.apache.org/content/repositories/orgapachecommons-1061/
>
> Builds and tests run fine.
>
>
On 12.11.14 10:23, Romain Manni-Bucau wrote:
> Hi
>
> I'm trying to align on commons standards this time.
>
> - here is the maven repo:
> https://repository.apache.org/content/repositories/orgapachecommons-1061/
Builds and tests run fine.
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666b
No idea, inheritance from previou sstructure surely
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2014-11-13 16:58 GMT+01:00 Gary Gregory :
> Why is the xdocs folder not under src/site?
>
> Gary
>
> On Wed, Nov 12, 2014
Why is the xdocs folder not under src/site?
Gary
On Wed, Nov 12, 2014 at 4:23 AM, Romain Manni-Bucau
wrote:
> Hi
>
> I'm trying to align on commons standards this time.
>
> - here is the maven repo:
> https://repository.apache.org/content/repositories/orgapachecommons-1061/
> - assemblies can b
Le 13 nov. 2014 10:51, "Johannes Weberhofer" a
écrit :
>
> Dear Romain,
>
> the packages are build nicely at my platform, here is my non-binding +1.
>
> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
> Maven home: /home.local/java/apache-maven-3
> Java ver
Dear Romain,
the packages are build nicely at my platform, here is my non-binding +1.
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
Maven home: /home.local/java/apache-maven-3
Java version: 1.7.0_71, vendor: Oracle Corporation
Java home: /usr/lib64/jvm
Hi
I'm trying to align on commons standards this time.
- here is the maven repo:
https://repository.apache.org/content/repositories/orgapachecommons-1061/
- assemblies can be found here
https://repository.apache.org/content/repositories/orgapachecommons-1061/org/apache/commons/commons-jcs-dist/2.
28 matches
Mail list logo
