RE: Unable to exclude .class files
Nope, not gonna do it... ball of mud stays. I can focus my efforts on newer
projects with a life ahead of them. This one can't change, too many years of
barnacles collecting.
Tom
-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Sent: Friday, March 05, 2010 6:52 PM
To: Maven Users List
Subject: Re: Unable to exclude .class files
Thomas Harris wrote:
When Mavenizing an existing project, especially one that is as old as Java,
you might find that the prying apart of the ball of mud via major refactoring
is a task that a client will not pay for. You still want to Mavenize the
project and integrate it into you blah/blah CI process, etc. So, in that
case...?
Tom
Someone will pay for and someone will reap the cost savings. In an ideal
world your customer pays for it and you get to reap the rewards. In
reality, you often pay for it and the customer gets the rewards when
your bills are less.
You are probably going to have to unravel good chunks of the ball of mud
anyway.
Ron
-Original Message-
From: thomas.k.sundb...@gmail.com [mailto:thomas.k.sundb...@gmail.com] On
Behalf Of Thomas Sundberg
Sent: Friday, March 05, 2010 4:40 AM
To: Maven Users List
Subject: Re: Unable to exclude .class files
Hi!
You should perhaps even have three projects. One for the common stuff,
one for the specific jar project that depends on the common stuff and
one for the sar project that also depends on the common stuff.
/Thomas
On Fri, Mar 5, 2010 at 10:35, Anders Hammar and...@hammar.net wrote:
No, you should have two separate projects. That's the Maven way - do
yourself a favor and don't fight it!
/Anders
On Fri, Mar 5, 2010 at 10:11, WriteJava ana...@plus.net wrote:
Thanks for your reply Anders, yes I am trying to build both jar and sar
within same maven project and I've some java classes which i need to add to
sar and exclude others and add them to jar. Is this possible?
Thanks
Anders Hammar wrote:
The exclude tag is for specifying artifactId:groupId as stated in the
docs.
I don't understand why you don't want to include the classes? If you have
a
sar project but don't want to include some classes, why do you have them
in
that project? Or could it be that you're trying to do a jar AND a sar in
the
same Maven project?
/Anders
On Thu, Mar 4, 2010 at 17:06, WriteJava ana...@plus.net wrote:
Hi,
I am trying to generate a sar file using 'jboss-packaging-maven-plugin'
plugin and I can't exclude .class files from my sar. It is including all
classes to sar. Can you please help? Here is my code snippet:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjboss-packaging-maven-plugin/artifactId
version2.1.1/version
extensionstrue/extensions
configuration
excludes
exclude**/*.class/exclude
/excludes
/configuration
executions
execution
idsar123/id
goals
goalsar/goal
/goals
phasepackage/phase
configuration
archiveNamemy-service/archiveName
deploymentDescriptorFile${basedir}/conf/mysarMETA-INF/jboss-service.xml/deploymentDescriptorFile
primaryArtifactfalse/primaryArtifact
/configuration
/execution
/executions
/plugin
Thanks
--
View this message in context:
http://old.nabble.com/Unable-to-exclude-.class-files-tp27782829p27782829.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Unable-to-exclude-.class-files-tp27782829p27791501.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Including sibling module attachment inside another module artifact
Wayne:
Thanks a lot for the headstart. I've got the first part of the solution working
now, however I'm having trouble figuring out how to specify the derived
attachment from module1 in the m-dependency-p:copy portion of it.
Here's a fragment from my module2's pom:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idcopy-installed/id
phaseinstall/phase
goals
goalcopy/goal
/goals
configuration
artifactItems
artifactItem
groupIdcom.x/groupId
artifactIdmodule1/artifactId
version${project.version}/version
typejar/type
/artifactItem
/artifactItems
outputDirectoryWebRoot/XXX/outputDirectory
/configuration
/execution
/executions
/plugin
Thing is, the artifact I want is the attachment, ie. it has a classifier
associated with it. The jar file is named module1-1.0.0-classifiername.jar. As
is, it doesn't even copy the non-classified file, so I've bungled something
else, and, even if it did work, there's no way to specify the classifier. What
to do?
Tom Harris
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Thursday, March 04, 2010 12:59 PM
To: Maven Users List
Subject: Re: Including sibling module attachment inside another module artifact
module1's output is two jar files, one the standard output, and the
other the extra one defined with includes/excludes using the
maven-jar-plugin and a classifier.
The extra one needs to be attached to your project with
build-helper-m-p and installed and deployed alongside the standard
output.
What I want to do is include this attachment inside the module2
war artifact, under that XXX folder. The WebRoot folder is defined to
be the staging area for the war artifact.
You should use m-dependency-p:copy to put the extra one in WebRoot.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Including sibling module attachment inside another module artifact
Wayne:
It now takes both the main artifact AND the classified attachment. Closer, but
still wrong. So odd.
Tom
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Friday, March 05, 2010 3:09 PM
To: Maven Users List
Subject: Re: Including sibling module attachment inside another module artifact
artifactItem
groupIdcom.x/groupId
artifactIdmodule1/artifactId
version${project.version}/version
typejar/type
classifierblah/classifier
Did you try this? The documentation doesn't show it, but the API [1]
has a getClassifier() which makes me think its there.
[1]
http://maven.apache.org/plugins/maven-dependency-plugin/apidocs/org/apache/maven/plugin/dependency/fromConfiguration/ArtifactItem.html
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Unable to exclude .class files
When Mavenizing an existing project, especially one that is as old as Java, you
might find that the prying apart of the ball of mud via major refactoring is a
task that a client will not pay for. You still want to Mavenize the project and
integrate it into you blah/blah CI process, etc. So, in that case...?
Tom
-Original Message-
From: thomas.k.sundb...@gmail.com [mailto:thomas.k.sundb...@gmail.com] On
Behalf Of Thomas Sundberg
Sent: Friday, March 05, 2010 4:40 AM
To: Maven Users List
Subject: Re: Unable to exclude .class files
Hi!
You should perhaps even have three projects. One for the common stuff,
one for the specific jar project that depends on the common stuff and
one for the sar project that also depends on the common stuff.
/Thomas
On Fri, Mar 5, 2010 at 10:35, Anders Hammar and...@hammar.net wrote:
No, you should have two separate projects. That's the Maven way - do
yourself a favor and don't fight it!
/Anders
On Fri, Mar 5, 2010 at 10:11, WriteJava ana...@plus.net wrote:
Thanks for your reply Anders, yes I am trying to build both jar and sar
within same maven project and I've some java classes which i need to add to
sar and exclude others and add them to jar. Is this possible?
Thanks
Anders Hammar wrote:
The exclude tag is for specifying artifactId:groupId as stated in the
docs.
I don't understand why you don't want to include the classes? If you have
a
sar project but don't want to include some classes, why do you have them
in
that project? Or could it be that you're trying to do a jar AND a sar in
the
same Maven project?
/Anders
On Thu, Mar 4, 2010 at 17:06, WriteJava ana...@plus.net wrote:
Hi,
I am trying to generate a sar file using 'jboss-packaging-maven-plugin'
plugin and I can't exclude .class files from my sar. It is including all
classes to sar. Can you please help? Here is my code snippet:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjboss-packaging-maven-plugin/artifactId
version2.1.1/version
extensionstrue/extensions
configuration
excludes
exclude**/*.class/exclude
/excludes
/configuration
executions
execution
idsar123/id
goals
goalsar/goal
/goals
phasepackage/phase
configuration
archiveNamemy-service/archiveName
deploymentDescriptorFile${basedir}/conf/mysarMETA-INF/jboss-service.xml/deploymentDescriptorFile
primaryArtifactfalse/primaryArtifact
/configuration
/execution
/executions
/plugin
Thanks
--
View this message in context:
http://old.nabble.com/Unable-to-exclude-.class-files-tp27782829p27782829.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Unable-to-exclude-.class-files-tp27782829p27791501.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Thomas Sundberg
M. Sc. in Computer Science
Mobile: +46 70 767 33 15
Blog: http://thomassundberg.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Including sibling module attachment inside another module artifact
Yeah, can't split up the code; 1. A lot of the code in the two artifacts is the same and, 2. This code is an existing project consisting of a enormous ball of mud, and the client will not pay for refactoring. The circular dependencies alone would make any decent programmer run screaming. I guess it's alright if we have both jars in the war subfolder; we will never reference the main artifact, and it makes the deployment ear bigger for no reason other than maven's idiosyncrasies. Eh. Yeah, sounds like a JIRA ticket is in order. By the time it's addressed, though, I will probably be long done with the project, and no one will ever revisit. :) Thanks for all your help, Wayne. Karma! Tom -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Friday, March 05, 2010 4:13 PM To: Maven Users List Subject: Re: Including sibling module attachment inside another module artifact It now takes both the main artifact AND the classified attachment. Closer, but still wrong. So odd. Except in very specific circumstances, I am not a fan of artifacts with classifiers. Reconfigure your project so that you have 2 separate modules and don't use classifier, and I'd assume it will work. But that does seem odd/wrong, so file a JIRA as well. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Unable to exclude .class files
The case I'm currently looking at would take many months of work to refactor to
split the modules up, whereas a build system is a build system. Our new
standard is Maven with Husdon and a bunch of code reporting tools, etc. We
really don't have a choice, except to use Maven or a different new build
system, like custom Ant scripts, as the old build system is all proprietary and
no longer supported by the vendor.
Tom
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of
Anders Hammar
Sent: Friday, March 05, 2010 4:14 PM
To: Maven Users List
Subject: Re: Unable to exclude .class files
Well, I believe that in most cases it's going to be more expensive fighting
Maven to force an nonstandard behavior instead of refactoring and going the
standard Maven path.
It's like doing C code style in Java. What's the benefit of switching to
Java?
/Anders
On Fri, Mar 5, 2010 at 21:22, Thomas Harris thar...@axispoint.com wrote:
When Mavenizing an existing project, especially one that is as old as Java,
you might find that the prying apart of the ball of mud via major
refactoring is a task that a client will not pay for. You still want to
Mavenize the project and integrate it into you blah/blah CI process, etc.
So, in that case...?
Tom
-Original Message-
From: thomas.k.sundb...@gmail.com [mailto:thomas.k.sundb...@gmail.com] On
Behalf Of Thomas Sundberg
Sent: Friday, March 05, 2010 4:40 AM
To: Maven Users List
Subject: Re: Unable to exclude .class files
Hi!
You should perhaps even have three projects. One for the common stuff,
one for the specific jar project that depends on the common stuff and
one for the sar project that also depends on the common stuff.
/Thomas
On Fri, Mar 5, 2010 at 10:35, Anders Hammar and...@hammar.net wrote:
No, you should have two separate projects. That's the Maven way - do
yourself a favor and don't fight it!
/Anders
On Fri, Mar 5, 2010 at 10:11, WriteJava ana...@plus.net wrote:
Thanks for your reply Anders, yes I am trying to build both jar and sar
within same maven project and I've some java classes which i need to add
to
sar and exclude others and add them to jar. Is this possible?
Thanks
Anders Hammar wrote:
The exclude tag is for specifying artifactId:groupId as stated in the
docs.
I don't understand why you don't want to include the classes? If you
have
a
sar project but don't want to include some classes, why do you have
them
in
that project? Or could it be that you're trying to do a jar AND a sar
in
the
same Maven project?
/Anders
On Thu, Mar 4, 2010 at 17:06, WriteJava ana...@plus.net wrote:
Hi,
I am trying to generate a sar file using
'jboss-packaging-maven-plugin'
plugin and I can't exclude .class files from my sar. It is including
all
classes to sar. Can you please help? Here is my code snippet:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjboss-packaging-maven-plugin/artifactId
version2.1.1/version
extensionstrue/extensions
configuration
excludes
exclude**/*.class/exclude
/excludes
/configuration
executions
execution
idsar123/id
goals
goalsar/goal
/goals
phasepackage/phase
configuration
archiveNamemy-service/archiveName
deploymentDescriptorFile${basedir}/conf/mysarMETA-INF/jboss-service.xml/deploymentDescriptorFile
primaryArtifactfalse/primaryArtifact
/configuration
/execution
/executions
/plugin
Thanks
--
View this message in context:
http://old.nabble.com/Unable-to-exclude-.class-files-tp27782829p27782829.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Unable-to-exclude-.class-files-tp27782829p27791501.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Thomas Sundberg
M. Sc. in Computer Science
Mobile: +46 70 767 33 15
Blog: http://thomassundberg.wordpress.com
Including sibling module attachment inside another module artifact
Maven Users: I have been searching for examples of how to make this work, but I must be missing something. We have a multimodule project, along these lines: proj-parent |- modules |- module1 |- target |- module1-1.0.0-classifiername.jar |- module2 |- WebRoot |- XXX module1's output is two jar files, one the standard output, and the other the extra one defined with includes/excludes using the maven-jar-plugin and a classifier. What I want to do is include this attachment inside the module2 war artifact, under that XXX folder. The WebRoot folder is defined to be the staging area for the war artifact. I have tried to use an assembly to do this, but it has no effect. The modules project defines this in its build plugins: plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptorsrc/assemble/classifiername.xml/descriptor /descriptors /configuration /plugin I put the classifiername.xml under the modules project in the src/assemble folder, and it contains: assembly xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0 http://maven.apache.org/xsd/assembly-1.1.0.xsdhttp://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0%20http:/maven.apache.org/xsd/assembly-1.1.0.xsd moduleSets moduleSet includes include*:module1/include /includes binaries attachmentClassifierclassifiername/attachmentClassifier outputDirectorymodule2/WebRoot/XXX/outputDirectory outputFileNameMappingfoo.jar/outputFileNameMapping /binaries /moduleSet /moduleSets /assembly But, when I run mvn clean install, the war file does not contain the file, and the build output never mentions it even tried to follow the instructions, no errors either. How do I get this to work? This artifact is a special jar that gets deployed to clients via the web using Java Web Start, and this is a port of an existing project, so I cannot change the internal folder layout of the war. (Names of the artifacts and projects have been changed to protect the innocent.) Tom Harris P.S. This was posted on Monday 3/1, but nobody responded at all, and our team really needs to move on this. Please help.
Including sibling module attachment inside another module artifact
Maven Users: I have been searching for examples of how to make this work, but I must be missing something. We have a multimodule project, along these lines: proj-parent |- modules |- module1 |- target |- module1-1.0.0-classifiername.jar |- module2 |- WebRoot |- XXX module1's output is two jar files, one the standard output, and the other the extra one defined with includes/excludes using the maven-jar-plugin and a classifier. What I want to do is include this attachment inside the module2 war artifact, under that XXX folder. The WebRoot folder is defined to be the staging area for the war artifact. I have tried to use an assembly to do this, but it has no effect. The modules project defines this in its build plugins: plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptorsrc/assemble/classifiername.xml/descriptor /descriptors /configuration /plugin I put the classifiername.xml under the modules project in the src/assemble folder, and it contains: assembly xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0 http://maven.apache.org/xsd/assembly-1.1.0.xsd; moduleSets moduleSet includes include*:module1/include /includes binaries attachmentClassifierclassifiername/attachmentClassifier outputDirectorymodule2/WebRoot/lib/outputDirectory outputFileNameMappingfoo.jar/outputFileNameMapping /binaries /moduleSet /moduleSets /assembly But, when I run mvn clean install, the war file does not contain the file, and the build output never mentions it even tried to follow the instructions, no errors either. How do I get this to work? This artifact is a special jar that gets deployed to clients via the web using Java Web Start, and this is a port of an existing project, so I cannot change the internal folder layout of the war. (Names of the artifacts and projects have been changed to protect the innocent.) Tom Harris
RE: Including sibling module attachment inside another module artifact
Correction: The assembly file should have actually said: outputDirectorymodule2/WebRoot/XXX/outputDirectory Typing error in the email... Still need help getting this to work. Thanks. Tom Harris -Original Message- From: Thomas Harris Sent: Monday, March 01, 2010 5:56 PM To: users@maven.apache.org Subject: Including sibling module attachment inside another module artifact Maven Users: I have been searching for examples of how to make this work, but I must be missing something. We have a multimodule project, along these lines: proj-parent |- modules |- module1 |- target |- module1-1.0.0-classifiername.jar |- module2 |- WebRoot |- XXX module1's output is two jar files, one the standard output, and the other the extra one defined with includes/excludes using the maven-jar-plugin and a classifier. What I want to do is include this attachment inside the module2 war artifact, under that XXX folder. The WebRoot folder is defined to be the staging area for the war artifact. I have tried to use an assembly to do this, but it has no effect. The modules project defines this in its build plugins: plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptorsrc/assemble/classifiername.xml/descriptor /descriptors /configuration /plugin I put the classifiername.xml under the modules project in the src/assemble folder, and it contains: assembly xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0 http://maven.apache.org/xsd/assembly-1.1.0.xsd; moduleSets moduleSet includes include*:module1/include /includes binaries attachmentClassifierclassifiername/attachmentClassifier outputDirectorymodule2/WebRoot/lib/outputDirectory outputFileNameMappingfoo.jar/outputFileNameMapping /binaries /moduleSet /moduleSets /assembly But, when I run mvn clean install, the war file does not contain the file, and the build output never mentions it even tried to follow the instructions, no errors either. How do I get this to work? This artifact is a special jar that gets deployed to clients via the web using Java Web Start, and this is a port of an existing project, so I cannot change the internal folder layout of the war. (Names of the artifacts and projects have been changed to protect the innocent.) Tom Harris - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version
Someone did fix this overnight, but they never sent any emails to the list regarding it. Guess they were embarrassed. Well, scratch my last post. And thanks, whoever cleaned up the repository mess. Tom -Original Message- From: Thomas Harris Sent: Tuesday, February 02, 2010 10:08 AM To: users@maven.apache.org Subject: RE: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version So, will someone replace the broken maven-site-plugin version 2.1 that was put onto the public repositories over this last weekend so we can get back to work? Our team is stuck until this is fixed. Any chance the person who broke it could replace the jar with the last working version 2.1 jar? Why does anyone except the maven committers have the ability to replace core parts of maven for everyone? Tom Harris Tired of having to make excuses to the management -- View this message in context: http://n2.nabble.com/SiteToolException-ArtifactNotFoundException-The-skin-does-not-exist-Unable-to-determine-the-release-n-tp4496008p4501310.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version
Friday, I was able to run the 'site' build on our project. This morning, I get the following error: [INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE We've changed nothing, so something bad has occurred to something out on the public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) on all platforms here when attempting to call mvn site on our project. I've updated this closed ticket. The ticket should be re-opened, as the same old problem is now occurring every 'site' build for us. Can someone please fix this soon? We cannot move forward on our project at this point. http://jira.codehaus.org/browse/MNG-3139 Tom
RE: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version
I attempted the workaround listed in the ticket (http://jira.codehaus.org/browse/MNG-3139), namely: 1. Create a /src/site/site.xml file in the top-level maven project, containing: [Code] project skin groupIdorg.apache.maven.skins/groupId artifactIdmaven-default-skin/artifactId version1.0/version /skin /project [/Code] Now the mvn site site-deploy works, however, there is no longer any links on the left-side menu, contrary to what I'd expect from a workaround. So, that's a bunk workaround. So, at this stage, our project is dead in the water until someone fixes the site plugin to get around this 'missing skin' defect. Every Hudson build fails with this error. Have users experienced similar issues in the past? How long does it usually take for a critical fix to get deployed to the central maven repos? Should I start writing the ant scripts for our projects? ;) Tom -Original Message- From: Thomas Harris Sent: Monday, February 01, 2010 1:26 PM To: users@maven.apache.org Subject: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Friday, I was able to run the 'site' build on our project. This morning, I get the following error: [INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE We've changed nothing, so something bad has occurred to something out on the public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) on all platforms here when attempting to call mvn site on our project. I've updated this closed ticket. The ticket should be re-opened, as the same old problem is now occurring every 'site' build for us. Can someone please fix this soon? We cannot move forward on our project at this point. http://jira.codehaus.org/browse/MNG-3139 Tom - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version
I have been using version 2.1 of the maven-site-plugin all along; When I had no site.xml file, I got all my menu items and they all worked. Now, without the site.xml file, the 'site' build fails as described. With the site.xml file detailed below, the 'site' build succeeds, however the resulting site has no links at all on the left hand side. :| Tom -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Monday, February 01, 2010 3:32 PM To: Maven Users List Subject: Re: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version On 2010-02-01 21:24, Thomas Harris wrote: I attempted the workaround listed in the ticket (http://jira.codehaus.org/browse/MNG-3139), namely: 1. Create a /src/site/site.xml file in the top-level maven project, containing: [Code] project skin groupIdorg.apache.maven.skins/groupId artifactIdmaven-default-skin/artifactId version1.0/version /skin /project [/Code] Now the mvn site site-deploy works, however, there is no longer any links on the left-side menu, contrary to what I'd expect from a workaround. So, that's a bunk workaround. Which version of the Site Plugin are you using? There is a bug in version 2.1 about missing menu links. So, at this stage, our project is dead in the water until someone fixes the site plugin to get around this 'missing skin' defect. Every Hudson build fails with this error. Have users experienced similar issues in the past? How long does it usually take for a critical fix to get deployed to the central maven repos? Should I start writing the ant scripts for our projects? ;) Tom -Original Message- From: Thomas Harris Sent: Monday, February 01, 2010 1:26 PM To: users@maven.apache.org Subject: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Friday, I was able to run the 'site' build on our project. This morning, I get the following error: [INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE We've changed nothing, so something bad has occurred to something out on the public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) on all platforms here when attempting to call mvn site on our project. I've updated this closed ticket. The ticket should be re-opened, as the same old problem is now occurring every 'site' build for us. Can someone please fix this soon? We cannot move forward on our project at this point. http://jira.codehaus.org/browse/MNG-3139 Tom - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
FW: Errors after upgrade to 2.2.1
I also found this JIRA ticket entered against a project named Maven Evangelism. Nice project. http://jira.codehaus.org/browse/MEV-649 However, switching down to log4j 1.2.14 changed nothing as far as these errors go. Perhaps some other library(s) also have this issue? If so, is there some simple way to tell Maven not to use this bogus repo? Previously... Manfred: What if we aren't running Nexus locally? I set up a VM on our network with Apache, and we're using that to host a repository folder and a place to deploy the site. But, we haven't even begun to look into installing Nexus locally. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:30 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Try mirrorOfexternal:*/mirrorOf with a local nexus instance to speed things up and then something like mirrors mirror idcentral/id nameLocalhost Nexus/name urlhttp://localhost:9081/nexus/content/groups/all/url mirrorOfexternal:*/mirrorOf /mirror /mirrors -- Manfred Moser http://www.mosabuam.com skype mosabua, twitter.com/mosabua http://www.linkedin.com/in/manfredmoser On Friday January 29 2010, Thomas Harris wrote: Muser, Manfred: I'm getting these same errors, but many many more of them. I did not have any reference to this oddball repository anywhere in my projects' pom.xml files, yet it seems Maven wants desperately to pull these jars from the ancient and deleted Maven 1 repository. I added this to my settings.xml, to no avail: mirrors mirror idjava.net2/id nameMirror of https://maven-repository.dev.java.net/nonav/repository//name urlhttp://download.java.net/maven/2//url mirrorOfjava.net/mirrorOf /mirror /mirrors Were you able to resolve this issue, Muser? How? Manfred, any ideas? Even though the build EVENTUALLY succeeds, these bogus lookups make our build like 20 times slower. Tom Harris Axispoint, Inc. Maven log output in question: [ERROR] Unable to determine if resource aopalliance:aopalliance:jar:1.0:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource apache-log4j:log4j:jar:1.2.14:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource asm:asm:jar:3.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib:jar:2.2:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib-nodep:jar:2.1_3:test exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-commons:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.abc.xyz.etp:proj-edoms-lib:jar:1.0.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-pm-if:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-pm-if\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-pm-if\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j
FW: Re: Errors after upgrade to 2.2.1
I'm getting these same errors, but many many more of them. I did not have any reference to this oddball repository anywhere in my projects' pom.xml files, yet it seems Maven wants desperately to pull these jars from the ancient and deleted Maven 1 repository. I added this to my settings.xml, to no avail: mirrors mirror idjava.net2/id nameMirror of https://maven-repository.dev.java.net/nonav/repository//name urlhttp://download.java.net/maven/2//url mirrorOfjava.net/mirrorOf /mirror /mirrors Were you able to resolve this issue, Muser? How? Manfred, any ideas? Even though the build EVENTUALLY succeeds, these bogus lookups make our build like 20 times slower. Tom Harris Axispoint, Inc. Maven log output in question: [ERROR] Unable to determine if resource aopalliance:aopalliance:jar:1.0:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource apache-log4j:log4j:jar:1.2.14:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource asm:asm:jar:3.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib:jar:2.2:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib-nodep:jar:2.1_3:test exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-commons:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\proj-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\proj-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\proj-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\proj-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\proj-commons\pom.xml exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.abc.xyz.etp:proj-edoms-lib:jar:1.0.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-pm-if:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\proj-pm-if\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\proj-pm-if\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\proj-pm-if\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\proj-pm-if\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\proj-pm-if\pom.xml exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.servlets:cos:jar:05Nov2002:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.sun.xml.bind:jaxb-impl:jar:2.1.10:provided exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.sun.xml.fastinfoset:FastInfoset:jar:1.2.7:provided exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.sun.xml.stream:sjsxp:jar:1.0.1:provided exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.thoughtworks.xstream:xstream:jar:1.3.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource
FW: Errors after upgrade to 2.2.1
I also found this JIRA ticket entered against a project named Maven Evangelism. Nice project name. :) http://jira.codehaus.org/browse/MEV-649 However, switching down to log4j 1.2.14 changed nothing as far as these errors go. Perhaps some other library(s) also have this issue? If so, is there some simple way to tell Maven not to use this bogus repo? Previously... Manfred: What if we aren't running Nexus locally? I set up a VM on our network with Apache, and we're using that to host a repository folder and a place to deploy the site. But, we haven't even begun to look into installing Nexus locally. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:30 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Try mirrorOfexternal:*/mirrorOf with a local nexus instance to speed things up and then something like mirrors mirror idcentral/id nameLocalhost Nexus/name urlhttp://localhost:9081/nexus/content/groups/all/url mirrorOfexternal:*/mirrorOf /mirror /mirrors -- Manfred Moser http://www.mosabuam.com skype mosabua, twitter.com/mosabua http://www.linkedin.com/in/manfredmoser On Friday January 29 2010, Thomas Harris wrote: Muser, Manfred: I'm getting these same errors, but many many more of them. I did not have any reference to this oddball repository anywhere in my projects' pom.xml files, yet it seems Maven wants desperately to pull these jars from the ancient and deleted Maven 1 repository. I added this to my settings.xml, to no avail: mirrors mirror idjava.net2/id nameMirror of https://maven-repository.dev.java.net/nonav/repository//name urlhttp://download.java.net/maven/2//url mirrorOfjava.net/mirrorOf /mirror /mirrors Were you able to resolve this issue, Muser? How? Manfred, any ideas? Even though the build EVENTUALLY succeeds, these bogus lookups make our build like 20 times slower. Tom Harris Axispoint, Inc. Maven log output in question: [ERROR] Unable to determine if resource aopalliance:aopalliance:jar:1.0:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource apache-log4j:log4j:jar:1.2.14:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource asm:asm:jar:3.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib:jar:2.2:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib-nodep:jar:2.1_3:test exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-commons:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.abc.xyz.etp:proj-edoms-lib:jar:1.0.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-pm-if:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-pm-if\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-pm-if\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules
RE: Errors after upgrade to 2.2.1
I put this into my settings.xml: mirrors mirror idexternal-redirect/id nameRedirect of external refs to local/name urlhttp://our.local.server.host/repository/url mirrorOfexternal:*/mirrorOf /mirror /mirrors Same errors occur in the log regardless of this change. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:37 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Thats fine too. Just try the mirror of external everything setting. I would really recommend looking at nexus on that server though. The repository is still just a filesystem but you have a lot of tooling around it via the webapp and you just run jetty/nexus instead of apache.. manfred -- Manfred Moser http://www.mosabuam.com skype mosabua, twitter.com/mosabua http://www.linkedin.com/in/manfredmoser On Friday January 29 2010, Thomas Harris wrote: Manfred: What if we aren't running Nexus locally? I set up a VM on our network with Apache, and we're using that to host a repository folder and a place to deploy the site. But, we haven't even begun to look into installing Nexus locally. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:30 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Try mirrorOfexternal:*/mirrorOf with a local nexus instance to speed things up and then something like mirrors mirror idcentral/id nameLocalhost Nexus/name urlhttp://localhost:9081/nexus/content/groups/all/url mirrorOfexternal:*/mirrorOf /mirror /mirrors Muser, Manfred: I'm getting these same errors, but many many more of them. I did not have any reference to this oddball repository anywhere in my projects' pom.xml files, yet it seems Maven wants desperately to pull these jars from the ancient and deleted Maven 1 repository. I added this to my settings.xml, to no avail: mirrors mirror idjava.net2/id nameMirror of https://maven-repository.dev.java.net/nonav/repository//name urlhttp://download.java.net/maven/2//url mirrorOfjava.net/mirrorOf /mirror /mirrors Were you able to resolve this issue, Muser? How? Manfred, any ideas? Even though the build EVENTUALLY succeeds, these bogus lookups make our build like 20 times slower. Tom Harris Axispoint, Inc. Maven log output in question: [ERROR] Unable to determine if resource aopalliance:aopalliance:jar:1.0:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource apache-log4j:log4j:jar:1.2.14:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource asm:asm:jar:3.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib:jar:2.2:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib-nodep:jar:2.1_3:test exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-commons:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.abc.xyz.etp:proj-edoms-lib:jar:1.0.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact
RE: Errors after upgrade to 2.2.1
I think I may know what's happening: http://n2.nabble.com/Suck-cannot-build-repository-down-td3432724.html#a3432724 Since I'm using the maven-project-info-reports-plugin:dependencies report, it does completely bypass the normal repository mechanism and thus Nexus. This sounds like a defect in the dependencies report portion of the codehaus mojo maven-project-info-reports-plugin. Does anyone know a workaround for this? I've spent a lot of time already on integrating Maven into our development process, and the deeper I go, the more problems crop up. Tom -Original Message- From: Thomas Harris Sent: Friday, January 29, 2010 4:58 PM To: manf...@mosabuam.com; mo...@yahoo-inc.com; users@maven.apache.org Subject: RE: Errors after upgrade to 2.2.1 I put this into my settings.xml: mirrors mirror idexternal-redirect/id nameRedirect of external refs to local/name urlhttp://our.local.server.host/repository/url mirrorOfexternal:*/mirrorOf /mirror /mirrors Same errors occur in the log regardless of this change. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:37 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Thats fine too. Just try the mirror of external everything setting. I would really recommend looking at nexus on that server though. The repository is still just a filesystem but you have a lot of tooling around it via the webapp and you just run jetty/nexus instead of apache.. manfred -- Manfred Moser http://www.mosabuam.com skype mosabua, twitter.com/mosabua http://www.linkedin.com/in/manfredmoser On Friday January 29 2010, Thomas Harris wrote: Manfred: What if we aren't running Nexus locally? I set up a VM on our network with Apache, and we're using that to host a repository folder and a place to deploy the site. But, we haven't even begun to look into installing Nexus locally. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:30 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Try mirrorOfexternal:*/mirrorOf with a local nexus instance to speed things up and then something like mirrors mirror idcentral/id nameLocalhost Nexus/name urlhttp://localhost:9081/nexus/content/groups/all/url mirrorOfexternal:*/mirrorOf /mirror /mirrors Muser, Manfred: I'm getting these same errors, but many many more of them. I did not have any reference to this oddball repository anywhere in my projects' pom.xml files, yet it seems Maven wants desperately to pull these jars from the ancient and deleted Maven 1 repository. I added this to my settings.xml, to no avail: mirrors mirror idjava.net2/id nameMirror of https://maven-repository.dev.java.net/nonav/repository//name urlhttp://download.java.net/maven/2//url mirrorOfjava.net/mirrorOf /mirror /mirrors Were you able to resolve this issue, Muser? How? Manfred, any ideas? Even though the build EVENTUALLY succeeds, these bogus lookups make our build like 20 times slower. Tom Harris Axispoint, Inc. Maven log output in question: [ERROR] Unable to determine if resource aopalliance:aopalliance:jar:1.0:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource apache-log4j:log4j:jar:1.2.14:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource asm:asm:jar:3.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib:jar:2.2:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib-nodep:jar:2.1_3:test exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-commons:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse
