Re: Regarding parsing of artifact details from Maven index file
Your best bet is to use the nexus-indexer api jar to access the data. This will keep you from having to deal with the contents, which in the old .zip are a lucene format but in the new .gz & incrementals is a special binary format. http://www.sonatype.com/people/2009/05/nexus-indexer-20-incremental-downloading/ http://repo2.maven.org/maven2/org/sonatype/nexus/nexus-indexer/2.0.0/ On Sat, May 30, 2009 at 3:51 AM, karthikeyan.laxman wrote: > > I need to get the details of list of artifacts contained in the index file > of > maven repository. I downloaded the nexus-maven-repository-indexes.zip file > from the repository and unzipped that file. But it is having .cfs and .gen > formatted files. How to parse that files to get the details (like artifact > id, group id, version, type, last modified timestamp) of all artifacts in > the index file. Is there any parser available for that? Can anyone help me > to solve this problem... > > -- > View this message in context: > http://www.nabble.com/Regarding-parsing-of-artifact-details-from-Maven-index-file-tp23791164p23791164.html > Sent from the Maven Developers mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Adding a new packaging
Hi Benjamin, Thanx, I have been able to write an initial version of the packaging plugin. One more small question what is the best place to override the properties like project.compileSourceRoots, project.build.outputDirectory etc. Do we have a plugin that does that? Regards, Nitin Verma On Sat, May 30, 2009 at 3:11 PM, Benjamin Bentmann wrote: > Nitin Verma wrote: > >> I looking at adding a packaging, that would have phases mapped to >> appropriate goals. >> >> Can some one guide me on how to add a new packaging? > > The section "Specifying a New Packaging" in [0] provides some hints. [1] > shows a minimal example plugin. > > > Benjamin > > > [0] > http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-lifecycle.apt?revision=501590 > [1] > http://svn.apache.org/viewvc/maven/core-integration-testing/trunk/core-it-support/core-it-plugins/maven-it-plugin-packaging/ > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE 3] maven-assembly-plugin 2.2-beta-4
I thought it was working great but...
what could cause this?
[INFO]
[INFO] Building Genesis
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting file set: /Users/david/geronimo/svn/geronimo/genesis/
trunk/target (included: [**], excluded: [])
[INFO] [assembly:single {execution: default}]
[INFO] Building tar : /Users/david/geronimo/svn/geronimo/genesis/trunk/
target/genesis-2.0-SNAPSHOT-source-release.tar.gz
[INFO] Building zip: /Users/david/geronimo/svn/geronimo/genesis/trunk/
target/genesis-2.0-SNAPSHOT-source-release.zip
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor]
[INFO] Unable to load parent project from a relative path: Could not
find the model file '/Users/david/geronimo/svn/geronimo/genesis/
pom.xml'. for project unknown
[INFO] Parent project loaded from repository.
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[INFO] [assembly:single {execution: default}]
[INFO] Building tar : /Users/david/geronimo/svn/geronimo/genesis/trunk/
target/genesis-2.0-SNAPSHOT-source-release.tar.gz
[INFO] Building zip: /Users/david/geronimo/svn/geronimo/genesis/trunk/
target/genesis-2.0-SNAPSHOT-source-release.zip
[INFO] [source:jar {execution: attach-sources}]
[INFO] [javadoc:jar {execution: attach-javadocs}]
[INFO] Not executing Javadoc as the project is not a Java classpath-
capable package
[INFO] [gpg:sign {execution: default}]
Reading passphrase from file descriptor 0
It seems to be building the source archives twice. I guess there the
same both times so all that is lost is some time so maybe its not a
big problem but with a big project its some time.
This particular example is https://svn.apache.org/repos/asf/geronimo/genesis/trunk
rev 780259 with maven 2.0.10
I only see this with multi-module projects: single module projects
only build the source-archive once.
I'm running
mvn clean install -Papache-release
the apache 6 pom is the parent
assembly plugin is configured in pluginManagement:
org.apache.maven.plugins
maven-assembly-plugin
2.2-beta-4
gnu
and run in apache-release profile:
org.apache.maven.plugins
maven-assembly-plugin
single
validate
truerunOnlyAtExecutionRoot>
source-release
org.apache
apache-source-release-
assembly-descriptor
1.0-SNAPSHOT
Assuming it's not a configuration problem, at this point I'd rather
have a release than wait more days to fix this but if its an easy
fix it would be great to only assemble once.
thanks
david jencks
On May 29, 2009, at 4:41 PM, John Casey wrote:
Hi again,
I've corrected the regressions from previous VOTEs for this
plugin, and I'm ready to try this once again...the URLs below have
been
updated where appropriate. Also note that I've staged the site
documentation, and included a link to that as well.
---
As I'm sure you've noticed, we've had a large thread on this list
regarding how to put together a proper ASF release using Maven. In
order
to enable the Assembly plugin to take on the burden of producing ASF
source-release assemblies, we had to fix a few bugs. Along with this,
I've also tackled the tar/zip file modes problem. The staged
repository
for this release can be found at:
https://repository.apache.org/content/repositories/maven-staging-035
The JIRA notes for the release can be found at the following URL, or
at
appended to the end of this message:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=111
Re: svn commit: r775049 - in /maven/plugins/trunk/maven-checkstyle-plugin: ./ src/main/java/org/apache/maven/plugin/checkstyle/ src/main/resources/config/ src/test/java/org/apache/maven/plugin/check
Sory, I missed time to follow this thread, thanks to benjamin for the ping. I applied MCHECKSTYLE-105 patch as is and did not detect the breacking changes, it can be rollbacked - I will check MCHECKSTYLE-101later. Following the thread about plugin and Java5 I've created a branch for checkstyle plugin : http://svn.apache.org/repos/asf/maven/plugins/branches/maven-checkstyle-plugin-java1.4/ This branch at revision just prior this commit, so we can just switch this branch with trunk to get a clean rollback. I could the create a java5 branch and apply MCHECKSTYLE-105 without the breacking changes to codestyle rules you noticed. Nicolas 2009/5/30 Benjamin Bentmann > Hi Nicolas, > > just a ping in case the former mails didn't make it through. > > > Benjamin > > > > Benjamin Bentmann wrote: > >> Dennis Lundberg wrote: >> >> it yet myself), you have changed the configuration for >>> HtmlPackage/JavadocPackage compared to how it used to work. IIUC >>> package.html files are no longer allowed in the configurations for >>> Avalon, Maven and Turbine. If we want to change that it's better to open >>> a separate issue for that, and commit that separately. I don't think we >>> should change the behavior, so I am -1 to the change in configuration. >>> >> >> Considering the brekaing effects on existing projects as pointed out by >> Dennis, Paul, Mark and the existing ITs, I agree with Dennis to revert this >> particular part of the commit. The requirement for per-package javadoc seems >> not to meet consensus in our community so the maven_checks.xml does not >> represent community style. >> >> Nicolas, can you comment on this topic please? Among others, there's also >> a question from Dennis about removal of the ASF license header unanswered as >> far as I see. >> >> >> Benjamin >> >
Re: [VOTE 3] maven-assembly-plugin 2.2-beta-4
John Casey wrote: I've corrected the regressions from previous VOTEs for this plugin, and I'm ready to try this once again.. Thanks for all your efforts on this plugin and the various upstream projects to bring us an easy source bundling tool. I kinda feel bad to say the following... https://repository.apache.org/content/repositories/maven-staging-035 The signature for the POM does not match, likely caused by usage of Maven 2.1.0 for the release. The source-release archives do not contain a LICENSE and NOTICE file as required by [0]. Due to this last issue, I think it's -1 for the release. Benjamin [0] http://www.apache.org/dev/release.html#full-copy-for-each-source-file - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r775049 - in /maven/plugins/trunk/maven-checkstyle-plugin: ./ src/main/java/org/apache/maven/plugin/checkstyle/ src/main/resources/config/ src/test/java/org/apache/maven/plugin/checkst
Hi Nicolas, just a ping in case the former mails didn't make it through. Benjamin Benjamin Bentmann wrote: Dennis Lundberg wrote: it yet myself), you have changed the configuration for HtmlPackage/JavadocPackage compared to how it used to work. IIUC package.html files are no longer allowed in the configurations for Avalon, Maven and Turbine. If we want to change that it's better to open a separate issue for that, and commit that separately. I don't think we should change the behavior, so I am -1 to the change in configuration. Considering the brekaing effects on existing projects as pointed out by Dennis, Paul, Mark and the existing ITs, I agree with Dennis to revert this particular part of the commit. The requirement for per-package javadoc seems not to meet consensus in our community so the maven_checks.xml does not represent community style. Nicolas, can you comment on this topic please? Among others, there's also a question from Dennis about removal of the ASF license header unanswered as far as I see. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Adding a new packaging
Nitin Verma wrote: I looking at adding a packaging, that would have phases mapped to appropriate goals. Can some one guide me on how to add a new packaging? The section "Specifying a New Packaging" in [0] provides some hints. [1] shows a minimal example plugin. Benjamin [0] http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-the-lifecycle.apt?revision=501590 [1] http://svn.apache.org/viewvc/maven/core-integration-testing/trunk/core-it-support/core-it-plugins/maven-it-plugin-packaging/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE 3] maven-assembly-plugin 2.2-beta-4
+1, I tried it with Archiva and I didn't see any problems in the generated tar and zip bundles. The links in the nav menu seems broken.. I'm not sure if the new staged site just hasn't been synched yet or if it is really broken. Thanks, Deng On Sat, May 30, 2009 at 4:41 AM, John Casey wrote: > Hi again, > > I've corrected the regressions from previous VOTEs for this > plugin, and I'm ready to try this once again...the URLs below have been > updated where appropriate. Also note that I've staged the site > documentation, and included a link to that as well. > > --- > > As I'm sure you've noticed, we've had a large thread on this list > regarding how to put together a proper ASF release using Maven. In order > to enable the Assembly plugin to take on the burden of producing ASF > source-release assemblies, we had to fix a few bugs. Along with this, > I've also tackled the tar/zip file modes problem. The staged repository > for this release can be found at: > > https://repository.apache.org/content/repositories/maven-staging-035 > > The JIRA notes for the release can be found at the following URL, or at > appended to the end of this message: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126&styleName=Html&version=15298 > > The website is staged at: > > http://maven.apache.org/plugins/maven-assembly-plugin-2.2-beta-4 > > NOTE: I staged one version of this website and it contained bad links. I've > just pushed another version up, and it should sync over soonish, so keep an > eye out. > > Please vote! > > [ ] +1 Pull the trigger! > [ ] +0 ...like I care > [ ] -1 Stop right there and back away from the plugin slowly! > > Here's my +1. > > Thanks! > > -john > > === > > > Release Notes - Maven 2.x Assembly Plugin - Version 2.2-beta-4 > > > ** Bug >* [MASSEMBLY-238] - Assembly plugin removes file permissions >* [MASSEMBLY-379] - Follow-up: file permissions are removed when > creating tar.gz assembly >* [MASSEMBLY-413] - Assembly plugin uses absolute paths from > project instance after interpolation >* [MASSEMBLY-414] - Allow regular expressions in include/exclude > patterns for filesets > > > > > --- > John Casey > Developer and PMC Member, Apache Maven (http://maven.apache.org) > Member, Apache Software Foundation > > "What we have to learn to do, we learn by doing." > -Aristotle > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Regarding parsing of artifact details from Maven index file
I need to get the details of list of artifacts contained in the index file of maven repository. I downloaded the nexus-maven-repository-indexes.zip file from the repository and unzipped that file. But it is having .cfs and .gen formatted files. How to parse that files to get the details (like artifact id, group id, version, type, last modified timestamp) of all artifacts in the index file. Is there any parser available for that? Can anyone help me to solve this problem... -- View this message in context: http://www.nabble.com/Regarding-parsing-of-artifact-details-from-Maven-index-file-tp23791164p23791164.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Adding a new packaging
Hi, I looking at adding a packaging, that would have phases mapped to appropriate goals. Can some one guide me on how to add a new packaging? Regards, Nitin Verma http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 edu.nitin simple javascript 1.0-SNAPSHOT simple ... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Adding a new packaging
+us...@maven.apache.org On Sat, May 30, 2009 at 1:34 AM, Nitin Verma wrote: > Hi, > > I looking at adding a packaging, that would have phases mapped to > appropriate goals. > > Can some one guide me on how to add a new packaging? > > Regards, > > Nitin Verma > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > edu.nitin > simple > javascript > 1.0-SNAPSHOT > simple > ... > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
