Sure. I can document this. I have already written the code that accounts
for the circularity problem. Instead of getting the stack overflow or
out of memory error it will throw a ProjectBuildingException and
identify both the failing artifact and the parent. However, I have to
retest this since
+1
--jason
On Mar 17, 2008, at 10:12 PM, Daniel Kulp wrote:
There is a critical bug in 1.0 where the resulting merged NOTICE files
may not be correct. This release is JUST to fix that issue (thus the
1.0.1 version and not 1.1):
http://jira.codehaus.org/browse/MSHADE-22
Staging area:
http:
Does this bundle have the same bits as the legal-bundle from genesis
does?
--jason
On Mar 17, 2008, at 10:05 PM, Daniel Kulp wrote:
To comply with the latest requirements discussed on legal-discuss, we
need a new version of the apache-jar-resource-bundle.
The only change is really the res
+1
--jason
On Mar 17, 2008, at 10:18 PM, Daniel Kulp wrote:
Several projects are sucessfully using remote-resources so it's time
pull
it out of beta and do the 1.0 release. :-)
This version provides three new improvements from 1.0-beta-2:
** Improvement
* [MRRESOURCES-22] - Provide
Hi all,
I wanted to bring up some interesting effects I've come across having
to do with the new import scope. In what I'd call conventional
cases, this feature seems to work just fine. These cases have been
covered in the core integration-tests for mng-3220. Basically, as
long as the re
The problem is that the site-stage mojo doesn't set my user's name and
the one @ apache is different from the one on my laptop.
I updated the doc.
Arnaud
On Sun, Mar 9, 2008 at 5:36 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 19, 2008 at 10:53 PM, Dan Fabulich <[EMAIL PROTECTED]> wr
The vote passed :
5 PMCs : Arnaud HERITIER, Fabrizio GIUSTINA, Carlos SANCHEZ, Olivier
LAMY, Emmanuel VENISSE
5 Committers : Dan TRAN, Nicolas DE LOOF, Fabrice BELLINGARD, Herve
BOUTEMY, Mauro TALEVI
3 Users : Siarhei DUDZIN, Paul BENEDICT, Richard VAN NIEUWENHOVEN
I deploy the release.
Thanks
+1
Daniel Kulp wrote:
There is a critical bug in 1.0 where the resulting merged NOTICE files
may not be correct. This release is JUST to fix that issue (thus the
1.0.1 version and not 1.1):
http://jira.codehaus.org/browse/MSHADE-22
Staging area:
http://people.apache.org/~dkulp/stage_shade/
+1
Daniel Kulp wrote:
To comply with the latest requirements discussed on legal-discuss, we
need a new version of the apache-jar-resource-bundle.
The only change is really the result of discussions and testing around:
http://jira.codehaus.org/browse/MRRESOURCES-32
Many thanks to David Jencks f
Oh sorry for the confusion. I changed my vote to 0, The IT is fixed by
locking down the versions, but it did show some incompatibilies in the
API that might need to be fixed.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 2:46 PM
To: Maven
What's the status on this Brian? I saw that you made a couple of commits
to the pom of IT 20. Did it solve your issues?
Can we proceed with the release, or are there any incompatibilities that
needs to be fixed?
Brian E. Fox wrote:
It could be, the old one must be lingering.
-Original M
+1
On Mar 17, 2008, at 11:12 AM, Daniel Kulp wrote:
There is a critical bug in 1.0 where the resulting merged NOTICE files
may not be correct. This release is JUST to fix that issue (thus the
1.0.1 version and not 1.1):
http://jira.codehaus.org/browse/MSHADE-22
Staging area:
http://people.a
The bootstrap should be fixed now, just FYI. It seems the bootstrap-
mini code, which the bootstrap.[sh|bat] scripts depend on, doesn't
track POM properties, and isn't smart enough to interpolate them into
dependency versions for now. My guess is, we didn't get bitten by $
{mavenVersion} the
+1
--
Olivier
2008/3/17, Daniel Kulp <[EMAIL PROTECTED]>:
>
> To comply with the latest requirements discussed on legal-discuss, we
> need a new version of the apache-jar-resource-bundle.
>
> The only change is really the result of discussions and testing around:
> http://jira.codehaus.org/bro
+1
--
Olivier
2008/3/17, Daniel Kulp <[EMAIL PROTECTED]>:
>
> Several projects are sucessfully using remote-resources so it's time pull
> it out of beta and do the 1.0 release. :-)
>
> This version provides three new improvements from 1.0-beta-2:
>
> ** Improvement
> * [MRRESOURCES-22] -
Hi guys,
I would like to close some issues.
Some [1] because the release of the archetype plugin version 2.0-alpha
has answered the needs.
And some others [2] that are obsoleted by the archetype plugin version
2.0-alpha.
Please feel free to comment on each issue by telling why i should not clos
+1
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 11:12 AM
To: Maven Developers List
Subject: [VOTE] Release maven-shade-plugin 1.0.1
There is a critical bug in 1.0 where the resulting merged NOTICE files
may not be correct. This release i
+1
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 11:06 AM
To: Maven Developers List
Subject: [VOTE] Release apache-jar-resource-bundle version 1.4
To comply with the latest requirements discussed on legal-discuss, we
need a new version of t
+1
On 17-Mar-08, at 8:18 AM, Daniel Kulp wrote:
Several projects are sucessfully using remote-resources so it's time
pull
it out of beta and do the 1.0 release. :-)
This version provides three new improvements from 1.0-beta-2:
** Improvement
* [MRRESOURCES-22] - Provide "excludes" for
+1
On 17-Mar-08, at 8:12 AM, Daniel Kulp wrote:
There is a critical bug in 1.0 where the resulting merged NOTICE files
may not be correct. This release is JUST to fix that issue (thus the
1.0.1 version and not 1.1):
http://jira.codehaus.org/browse/MSHADE-22
Staging area:
http://people.apach
+1
On 17-Mar-08, at 8:05 AM, Daniel Kulp wrote:
To comply with the latest requirements discussed on legal-discuss, we
need a new version of the apache-jar-resource-bundle.
The only change is really the result of discussions and testing
around:
http://jira.codehaus.org/browse/MRRESOURCES-32
Continuum was running it for a while, but it kept going down (admittedly
it was possibly a system problem). Every time I tried to find out the
results of a test, someone had to go kick it first because it wasn't
running. This was an ongoing problem for a long time and no one
apparently had the time
On Mon, Mar 17, 2008 at 4:14 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> ci.sonatype.org for now. It is what I'm relying on while doing the 2.0.9
> release. Neither of the CI systems are currently publishing snapshots to
> the official apache repo due to various infrastructure issues we'll wor
Well, I took a pretty careful look at things before I made this
switch, and even made a couple of attempts that failed in the various
testing stages.
As far as I could tell, the process-project cache is not used at all
for inheritance calculations (assembleLineage calls itself
recursively
ci.sonatype.org for now. It is what I'm relying on while doing the 2.0.9
release. Neither of the CI systems are currently publishing snapshots to
the official apache repo due to various infrastructure issues we'll work
out soon.
-Original Message-
From: Siarhei Dudzin [mailto:[EMAIL PROTEC
Several projects are sucessfully using remote-resources so it's time pull
it out of beta and do the 1.0 release. :-)
This version provides three new improvements from 1.0-beta-2:
** Improvement
* [MRRESOURCES-22] - Provide "excludes" for artifacts that are passed
into velocity
* [MRRE
There is a critical bug in 1.0 where the resulting merged NOTICE files
may not be correct. This release is JUST to fix that issue (thus the
1.0.1 version and not 1.1):
http://jira.codehaus.org/browse/MSHADE-22
Staging area:
http://people.apache.org/~dkulp/stage_shade/
Tag:
http://svn.apache.
To comply with the latest requirements discussed on legal-discuss, we
need a new version of the apache-jar-resource-bundle.
The only change is really the result of discussions and testing around:
http://jira.codehaus.org/browse/MRRESOURCES-32
Many thanks to David Jencks for leading that up with
So what's going to be the major CI server for Maven?
Regards,
Siahrei
On Mon, Mar 17, 2008 at 1:30 PM, Brian E. Fox <[EMAIL PROTECTED]>
wrote:
> My plan is to move the rest of the stuff over to Hudson this week.
>
> -Original Message-
> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> S
My plan is to move the rest of the stuff over to Hudson this week.
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 3:55 AM
To: Maven Developers List
Subject: CI for Maven
Hi all,
I noticed that archiva and continuum are now building on v
+1
Emmanuel
On Sat, Mar 15, 2008 at 1:30 AM, Arnaud HERITIER <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> We solved more than 50 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593&styleName=Html&projectId=11133
> Important changes are :
> - Add support for WTP 2.0
> - Add support
+1
Arnaud HERITIER wrote:
Hi,
We solved more than 50 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593&styleName=Html&projectId=11133
Important changes are :
- Add support for WTP 2.0
- Add support for MyEclipse
- Improve RAD6 support
- Posibility to discover projects in th
+1
--
Olivier
2008/3/15, Arnaud HERITIER <[EMAIL PROTECTED]>:
> Hi,
>
> We solved more than 50 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593&styleName=Html&projectId=11133
> Important changes are :
> - Add support for WTP 2.0
> - Add support for MyEclipse
> - Im
Hi all,
I noticed that archiva and continuum are now building on vmbuild
instead of maven.zone. I think it is to have a better stability. Can't
we move others build o it (plugins, core ...). Or perhaps on hudson @
Sonatype. I don't know what is the best.
Arnaud
--
..
+1
Ritchie
Arnaud HERITIER wrote:
> Hi,
>
> We solved more than 50 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593&styleName=Html&projectId=11133
> Important changes are :
> - Add support for WTP 2.0
> - Add support for MyEclipse
> - Improve RAD6 support
> - Posibility t
Hi Chris,
You can simply use properties in an activated profile of your settings.xml,
see
http://maven.apache.org/ref/current/maven-settings/settings.html#class_profile
Then properties are simply referenced in your pom as ${property name}.
That would be something like the following in your pom.xm
Hi
I'm trying to SIGN jar files using the sign goal with the maven JAR
plugin. To sign a jar file, you would use the following code in your
pom.xml file as an example:
${artifactId}-${version}
org.apache.maven.plugins
37 matches
Mail list logo
