I think the problem comes from a transitive dependency in jenkins that
depends explicitly on glassfish (even though jenkins has changed their
dependencies as well) I will do a new build with an empty repository to
check.
On 17.03.2012 11:26, Mauro Talevi wrote:
The dependency on glassfish as been removed in latest snapshot. The only
artifacts not in Maven Central are the atlassian ones. If you build with
the -s settings.xml you should be fine. If not, let us know what it is
the problem.
Cheers
On 16/03/2012 22:00, Alexander Lehmann wrote:
There are still issues with building the jenkins and hudson modules
due to the unavailability of maven.glassfish.org. I wonder if it would
be helpful if the two modules are moved to a new separate project?
Jenkins has a maven repository for their artifacts, but that is not
needed by the other modules, this could be in the settings.xml for the
hudson/jenkins project, while the core project keeps its settings.
bye, Alexander
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
