On Fri, May 7, 2010 at 3:44 PM, Jason Dillon wrote:
> Its the repo trigger that is barfing... it will soon be replaced. You can
> ignore this error, it only means that Hudson will not be able to trigger the
> build when a SNAPSHOT changed.
Ok.
I was looking in the hopes of finding the configu
Its the repo trigger that is barfing... it will soon be replaced. You can
ignore this error, it only means that Hudson will not be able to trigger the
build when a SNAPSHOT changed.
--jason
On May 6, 2010, at 10:44 PM, Barrie Treloar wrote:
> There are errors but the build is marked as succe
There are errors but the build is marked as success.
Could someone look into this please?
See https://grid.sonatype.org/ci/view/Maven/job/Maven-2.2.x/72/console
The error is:
Triggering 1.5,windows
hudson.util.IOException2: remote file operation failed
at hudson.FilePath.act(FilePath.java
Issue Subscription
Filter: Design & Best Practices (23 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
Don't go back to a lower version in the parent unless you change one
if the other coords like the artifactid. This causes sorting issues
when the metadata needs to be rebuilt.
--Brian (mobile)
On May 6, 2010, at 4:29 PM, Hervé BOUTEMY
wrote:
ok
i'll do the svn update and open a Xircle
ok
i'll do the svn update and open a Xircles chord to create ARCHETYPES project
Regards,
Hervé
Le samedi 01 mai 2010, Hervé BOUTEMY a écrit :
> After releasing an alpha of Archetype components and some archetypes, it
> becomes clear to me that the actual structure is not ideal.
>
> I think that
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=16445
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MSHARED+AND+component+%3D+maven-archiver+AND+status+%3D+Open
On 06/05/2010, at 7:23 PM, Kristian Rosenvold wrote:
> I'm about to start releasing plugins and libraries, and I have come to
> realize I'm a terrible neat-nick ;)
>
> I look at the dependencies on maven-archiver and I see that several of
> them appear unused, and some can be trimmed down to les
I'm about to start releasing plugins and libraries, and I have come to
realize I'm a terrible neat-nick ;)
I look at the dependencies on maven-archiver and I see that several of
them appear unused, and some can be trimmed down to less invasive
scopes, such as provided.
Is there any reason why:
