Re: standardized Maven GAV URN?
is le last part type or packaging ? 2010/6/29 Brian Fox bri...@infinity.nu Group:artifact:version:classifier:extension is pretty common On Jun 26, 2010, at 1:39 PM, lukewpatterson lukewpatter...@gmail.com wrote: It would be nice to be able to represent any Maven GAV in a string. Does such a standard exist? A good use case is for plugins that allow input configuration file paths. If there was a reusable component that took an ArtifactResolver and a String, then any plugins that currently accept file locations as Strings could passively add GAV capability. e.g. with Clover plugin, I can give the path for the license file, but if I want to store the license in the company's internal Maven repo (and thus get the advantage of Maven versioning), I have to jump through some dependency plugin hoops to get it in the right place at the right time. I'd like to be able to just give the Clover plugin a GAV URN and have it download what it needs -- View this message in context: http://maven.40175.n5.nabble.com/standardized-Maven-GAV-URN-tp511480p511480.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
Re: standardized Maven GAV URN?
On Tue, Jun 29, 2010 at 8:34 AM, nicolas de loof nicolas.del...@gmail.com wrote: is le last part type or packaging ? Is there a difference? -- Germanys national anthem is the most boring in the world - how telling! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: standardized Maven GAV URN?
sorry, I mean packaging vs extension. ejb packaging creates a jar extension 2010/6/29 Jochen Wiedmann jochen.wiedm...@gmail.com On Tue, Jun 29, 2010 at 8:34 AM, nicolas de loof nicolas.del...@gmail.com wrote: is le last part type or packaging ? Is there a difference? -- Germanys national anthem is the most boring in the world - how telling! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Assembly downloads the file and then can not find the file
The install generates the following odd error where it seems to find and
download the 2 artifacts that I specified in the pom but then can not
find them to build the tar and jar.
Any suggestions?
The assembly descriptor follows the log info.
Ron
[INFO] Scanning for projects...
[INFO]
[INFO] Building lms-deploymentjars
[INFO]task-segment: [install]
[INFO]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [assembly:single {execution: create-jar-deployment-archive}]
[INFO] Reading assembly descriptor: src/assembly/lms-deployment-archives.xml
[INFO] Processing DependencySet (output=null)
Downloading:
http://xxx/nexus/content/groups/public/com/artifact_software/lms/lms-pom-spring-hibernate-mysql-tomcat/1.8.3-SNAPSHOT/lms-pom-spring-hibernate-mysql-tomcat-1.8.3-20100527.163839-1.jar
Downloading:
http://xxx/nexus/content/groups/public/com/artifact_software/lms/lms-pom-jsf/1.8.3-SNAPSHOT/lms-pom-jsf-1.8.3-20100527.172209-1.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to create assembly: Failed to resolve dependencies for
project: com.artifact_software.lms:lms-deployment-jars:pom:1.8.3-SNAPSHOT
Missing:
--
1)
com.artifact_software.lms:lms-pom-spring-hibernate-mysql-tomcat:jar:1.8.3-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.artifact_software.lms
-DartifactId=lms-pom-spring-hibernate-mysql-tomcat
-Dversion=1.8.3-20100527.163839-1 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the
file there:
mvn deploy:deploy-file -DgroupId=com.artifact_software.lms
-DartifactId=lms-pom-spring-hibernate-mysql-tomcat
-Dversion=1.8.3-20100527.163839-1 -Dpackaging=jar -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) com.artifact_software.lms:lms-deployment-jars:pom:1.8.3-SNAPSHOT
2)
com.artifact_software.lms:lms-pom-spring-hibernate-mysql-tomcat:jar:1.8.3-SNAPSHOT
2) com.artifact_software.lms:lms-pom-jsf:jar:1.8.3-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.artifact_software.lms
-DartifactId=lms-pom-jsf -Dversion=1.8.3-20100527.172209-1
-Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the
file there:
mvn deploy:deploy-file -DgroupId=com.artifact_software.lms
-DartifactId=lms-pom-jsf -Dversion=1.8.3-20100527.172209-1
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) com.artifact_software.lms:lms-deployment-jars:pom:1.8.3-SNAPSHOT
2) com.artifact_software.lms:lms-pom-jsf:jar:1.8.3-SNAPSHOT
--
2 required artifacts are missing.
for artifact:
com.artifact_software.lms:lms-deployment-jars:pom:1.8.3-SNAPSHOT
from the specified remote repositories:
nexus
(http://repo.artifact-software.com:8081/nexus/content/groups/public)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 10 seconds
[INFO] Finished at: Tue Jun 29 11:56:46 EDT 2010
[INFO] Final Memory: 13M/24M
[INFO]
My assembly descriptor looks like this:
assembly
idlms-deployment-jars/id
formats
formattar/format
formatzip/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
dependencySets
dependencySet
includes/
/dependencySet
/dependencySets
/assembly
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Multi project release without SCM
I have a good working multiproject release but no SCM setup yet (I'm waiting for BRZ to be installed to replace CVS). Currently the parent pom has version 1.10-SNAPSHOT configured. The component's pom refer to this pom. If I want to release 1.10, do I need to modify all the pom's and remove -SNAPSHOT? release:prepare does not work because of the missing SCM. -- View this message in context: http://maven.40175.n5.nabble.com/Multi-project-release-without-SCM-tp511922p511922.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
mvn release:stage
Hi, I do not see that much docs on this release plugin goal and I'm not sure if anyone has used it before. Does anyone knows where I can find some docs that can help me resolve some issues I'm facing? Thanks, ABA
Assembly includes too many files.
This assembly puts the dependencies in the archives but also seems to include the transitive dependencies of the jars and adds them as well. This is not what I want since the top level jars were built by the assembly plug-in as a jar-with-dependencies and contain all of the dependencies already. So I am ending up with 2 copies of every bottom level jar(one at the top level of the tar and another inside the jar-with-dependencies jar. assembly idlms-deployment-jars/id formats formattar/format formatzip/format /formats includeBaseDirectoryfalse/includeBaseDirectory unpacktrue/unpack dependencySets dependencySet /dependencySet /dependencySets /assembly I want to exclude all of the transitive dependencies. can I do this or is there a better way to build a tar of a set of jar-with-dependencies jar files? Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
making a repository read-only
Hi all, I've got the requirement of providing different settings.xml files to different clients. Currently we've got different repositories: Third Party (TP), SNAPSHOTS and Releases. Each client has got different requirements. For instance, developers can only use all repositories as read-only, our CI environment can upload artifacts to the SNAPSHOT but have read-only access to TP and Releases while our build software can only upload to Releases but have read-only to TP and SNAPSHOTS. Is there a way to setup this kind of configuration via settings.xml or other elements inside a POM? So far it seems I couldn't find a way. Regards, M. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: making a repository read-only
Hi all, I've got the requirement of providing different settings.xml files to different clients. Currently we've got different repositories: Third Party (TP), SNAPSHOTS and Releases. Each client has got different requirements. For instance, developers can only use all repositories as read-only, our CI environment can upload artifacts to the SNAPSHOT but have read-only access to TP and Releases while our build software can only upload to Releases but have read-only to TP and SNAPSHOTS. Is there a way to setup this kind of configuration via settings.xml or other elements inside a POM? So far it seems I couldn't find a way. Just use different username/password combinations in your repository server with different access rights and use the different roles in pom.xml profiles and settings.xml. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: making a repository read-only
Can you not do this on your repository? Are you using Nexus? Ron On 29/06/2010 7:06 PM, Jemos Infra wrote: Hi all, I've got the requirement of providing different settings.xml files to different clients. Currently we've got different repositories: Third Party (TP), SNAPSHOTS and Releases. Each client has got different requirements. For instance, developers can only use all repositories as read-only, our CI environment can upload artifacts to the SNAPSHOT but have read-only access to TP and Releases while our build software can only upload to Releases but have read-only to TP and SNAPSHOTS. Is there a way to setup this kind of configuration via settings.xml or other elements inside a POM? So far it seems I couldn't find a way. Regards, M. - 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: making a repository read-only
No, we don't use Nexus, just the file system. We've got a single account (sys_account) who is entitled to upload to this repository through ssh using an infrastructure given key, so also the possibility to use multiple usernames/passwords doesn't seem feasable. Any other suggestions? Regards, M. On Tue, 2010-06-29 at 16:22 -0700, Manfred Moser wrote: Hi all, I've got the requirement of providing different settings.xml files to different clients. Currently we've got different repositories: Third Party (TP), SNAPSHOTS and Releases. Each client has got different requirements. For instance, developers can only use all repositories as read-only, our CI environment can upload artifacts to the SNAPSHOT but have read-only access to TP and Releases while our build software can only upload to Releases but have read-only to TP and SNAPSHOTS. Is there a way to setup this kind of configuration via settings.xml or other elements inside a POM? So far it seems I couldn't find a way. Just use different username/password combinations in your repository server with different access rights and use the different roles in pom.xml profiles and settings.xml. - 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
