Re: source and javadoc jars from test-jar

packaging is `jar` not `test-jar` there is only one artifact with `test-jar` packaging, namely the `test-jar` You want to use org.apache.juddi:**uddi-tck:jar:test-sources org.apache.juddi:**uddi-tck:jar:test-javadoc Not a bug On 4 June 2013 14:02, Kurt T Stam wrote: I'm assuming it is a bu

Re: source and javadoc jars from test-jar

I'm assuming it is a bug and opened http://jira.codehaus.org/browse/MSOURCES-66 On 6/3/13 2:26 PM, Kurt T Stam wrote: Hi guys, I'm trying to add 'test-jar' resources to my assembly; i.e. the following jars are created by one of our other modules: main: -rw-r--r-- 1 ks

source and javadoc jars from test-jar

Hi guys, I'm trying to add 'test-jar' resources to my assembly; i.e. the following jars are created by one of our other modules: main: -rw-r--r-- 1 kstam admin 11603 Jun 3 11:29 uddi-tck-3.2.0-SNAPSHOT.jar -rw-r--r-- 1 kstam admin 27880 Jun 3 11:29 uddi-tck-3.2.0-SNAPSHOT-jav

Re: release plugin and singing (missing MD5 and SHA1)

Turns out I wasn't using maven 3.0.3 but a 3.0.4-SNAPSHOT. When I figured that out and went back to 3.0.3 things are working. Cheers, -Kurt On 1/24/12 9:48 PM, Kurt T Stam wrote: Actually that command seems to make the hash files in my local repo, however mvn release:preform -Pa

Re: release plugin and singing (missing MD5 and SHA1)

apache/juddi/scout/scout/1.2.4/scout-1.2.4-javadoc.jar.sha1'. -*Missing MD5:* '/org/apache/juddi/scout/scout/1.2.4/scout-1.2.4-javadoc.jar.md5.' -*Missing SHA1:* '/org/apache/juddi/scout/scout/1.2.4/scout-1.2.4.pom.sha1'. -*Missing MD5:* '/org/apache/judd

release plugin and singing (missing MD5 and SHA1)

Hi guys, I'm trying to release Apache Scout and it is creating signed (.asc) files, but not the MD5 and SHA1 hash files. Last time it did, I must be doing something different. I'm running mvn clean install -Papache-release Any hint would be very welcome! Cheers, --Kurt --

Re: Maven not pulling down latest snapshot jar issue

between theory and practice, but in practice, there is ... On Fri, Sep 30, 2011 at 2:44 PM, Kurt T Stam wrote: Thanks Robert, I tried replacing the aether jar from 1.11 to 1.12 but that did not fix my issue. In my case the meta data is nicely updated by the actual jar and pom etc are still

Re: Maven not pulling down latest snapshot jar issue

Thanks Robert, I tried replacing the aether jar from 1.11 to 1.12 but that did not fix my issue. In my case the meta data is nicely updated by the actual jar and pom etc are still old. I guess I will spend some time with the debugger over the weekend to see what's going on. If anyone has so

Maven not pulling down latest snapshot jar issue

1. I'm using maven-3.0.3 and does anyone else have the issue where the latest snapshot jar is NOT downloaded while the meta data IS updated? It sounds a lot like what's being described in this bug report, although the title is misleading http://jira.codehaus.org/browse/MNG-4142, ad it happens

Re: Supporting different build artifact of the same code base

d the scenes you might have a third module which contains just the source and you package up that source and unpack it for the two modules... or you could get away with m-shade-p producing an uber-jar On 17 June 2011 16:21, Kurt T Stam wrote: Hi maven users, On the jUDDI project we have a ne

Supporting different build artifact of the same code base

Hi maven users, On the jUDDI project we have a need to support compiling against 2 different version of the jax-ws spec (2.1 and 2.2). How do we go about this? We can make profiles with different classifiers but some people argue for 1 build artifact for each module, and this way we'd be produ