continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Louis Smith <dr.louis.sm...@gmail.com>
Subject Re: SNAPSHOT issue on 1.4.1
Date Tue, 22 May 2012 11:39:52 GMT
What I mean is that when I do an "install" at all - a new timestamped
version is created - not a "1.0.2-SNAPSHOT" which is what should be
created.  Here is a text convert of the links I sent.  As you can see, each
time I ran the install, it creates a new version (-1.pom, -2.pom), but all
have a timestamp in the name which shouldn't be there.  This is a "master
pom" project and I'm working on getting the reports to run (finally
discovered there is a bug in APIViz under JDK 1.7 - so converting to
UMLGraph for now).  Since the install doesn't create the desired/expected
file (components-pom-1.0.2-SNAPSHOT.pom), my other projects can't reference
it.  I have to keep doing a release and use the "live" version for testing.



components-pom-1.0.2-20120519.090019-1.pom         20-May-2012 16:33 15K
components-pom-1.0.2-20120519.090019-1.pom.md5 20-May-2012 16:33 32
components-pom-1.0.2-20120519.090019-1.pom.sha1 20-May-2012 16:33 40
components-pom-1.0.2-20120519.090019-2.pom         20-May-2012 18:13 15K
components-pom-1.0.2-20120519.090019-2.pom.md5 20-May-2012 18:13 32
components-pom-1.0.2-20120519.090019-2.pom.sha1 20-May-2012 18:13 40
components-pom-1.0.2-20120519.090019-3.pom         20-May-2012 18:14 15K
components-pom-1.0.2-20120519.090019-3.pom.md5 20-May-2012 18:14 32
components-pom-1.0.2-20120519.090019-3.pom.sha1 20-May-2012 18:14 40
components-pom-1.0.2-20120519.090019-4.pom         21-May-2012 05:00 15K
components-pom-1.0.2-20120519.090019-4.pom.md5 21-May-2012 05:00 32
components-pom-1.0.2-20120519.090019-4.pom.sha1 21-May-2012 05:00 40
components-pom-1.0.2-20120519.090019-5.pom         22-May-2012 05:00 15K
components-pom-1.0.2-20120519.090019-5.pom.md5 22-May-2012 05:00 32
components-pom-1.0.2-20120519.090019-5.pom.sha1 22-May-2012 05:00 40
maven-metadata.xml 22-May-2012 05:00 374
maven-metadata.xml.md5 22-May-2012 05:00 32
maven-metadata.xml.sha1 22-May-2012 05:00 40


I also have the issue on "war" projects - it is creating that "cut off at
4K" pom file again as shown here..  I know that was solved before, so I'm
searching for that solution to re-implement.  This is running on a 5AM
schedule - I'm not actually up every day at 5...

You can see that all the time-stamped pom files are 4.0K bytes - but the
valid one (which is created, unlike in the example above) is the correct
size.

  -
black-port-1.0.0-20120424.180259-1.pom 25-Apr-2012 12:29 4.0K
black-port-1.0.0-20120424.180259-1.pom.md5 25-Apr-2012 12:29 32
black-port-1.0.0-20120424.180259-1.pom.sha1 25-Apr-2012 12:29 40
black-port-1.0.0-20120424.180259-1.war 25-Apr-2012 12:29 14M
black-port-1.0.0-20120424.180259-1.war.md5 25-Apr-2012 12:29 32
black-port-1.0.0-20120424.180259-1.war.sha1 25-Apr-2012 12:29 40
black-port-1.0.0-20120424.180259-2.pom 25-Apr-2012 12:31 4.0K
black-port-1.0.0-20120424.180259-2.pom.md5 25-Apr-2012 12:31 32
black-port-1.0.0-20120424.180259-2.pom.sha1 25-Apr-2012 12:31 40
black-port-1.0.0-20120424.180259-2.war 25-Apr-2012 12:31 14M
black-port-1.0.0-20120424.180259-2.war.md5 25-Apr-2012 12:31 32
black-port-1.0.0-20120424.180259-2.war.sha1 25-Apr-2012 12:31 40

.... snip out a month of duplicates...down to the run on 15-May.  As you
can see, it creates the "timestamp" version with the bad pom, the right
 14M war, and then the final correct pom and war.  And that the "timestamp"
is no where near the current date/time - so I have no clue where that is
coming from.


black-port-1.0.0-20120426.170033-28.pom         15-May-2012 05:00 4.0K
black-port-1.0.0-20120426.170033-28.pom.md5 15-May-2012 05:00 32
black-port-1.0.0-20120426.170033-28.pom.sha1 15-May-2012 05:00 40
black-port-1.0.0-20120426.170033-28.war         15-May-2012 05:00 14M
black-port-1.0.0-20120426.170033-28.war.md5 15-May-2012 05:00 32
black-port-1.0.0-20120426.170033-28.war.sha1 15-May-2012 05:00 40
black-port-1.0.0-SNAPSHOT.pom                         15-May-2012 05:00 26K

black-port-1.0.0-SNAPSHOT.war                         15-May-2012 05:00 14M

maven-metadata-deployment-repository.xml         15-May-2012 05:00 365
maven-metadata-deployment-repository.xml.sha1 15-May-2012 05:00 40
maven-metadata-local.xml 15-May-2012 05:00 318
maven-metadata.xml 15-May-2012 05:00 365
maven-metadata.xml.md5 15-May-2012 05:00 32
maven-metadata.xml.sha1 15-May-2012 05:00 40


All this testing is on a new clean install of UBUNTU, JDK 1.7, Glassfish
3.1.1, Continuum 1.4.1-SNAPSHOT (testing to help push it to release!!!!)

Louis

On Mon, May 21, 2012 at 10:37 PM, Brett Porter <brett@apache.org> wrote:

> Hi Louis,
>
> "mvn clean install" is sufficient - that implies the compile and package
> steps of the lifecycle. Does that help?
>
> I'm afraid I don't quite understand the problem otherwise - I may be a bit
> confused since the output was converted to plaintext and isn't quite clear.
>
> - Brett
>
> On 22/05/2012, at 4:01 AM, Louis Smith wrote:
>
> > I noticed that when I am working on  a jar file, and I re-run "clean
> > compile package install" of a -SNAPSHOT of a project while developing and
> > testing, that the "install" directory is NOT clean.. it has
> "time-stamped"
> > files in it, and my other builds can't reference it.
> >
> > What I see is:
> >
> >
> > Parent Directory<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/
> >
> > - [image: [ ]]components-pom-1.0.2-20120519.090019-1.pom<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-1.pom
> >20-May-2012
> > 16:3315K [image: [
> > ]]components-pom-1.0.2-20120519.090019-1.pom.md5<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-1.pom.md5
> >20-May-2012
> > 16:3332 [image: [
> > ]]components-pom-1.0.2-20120519.090019-1.pom.sha1<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-1.pom.sha1
> >20-May-2012
> > 16:3340 [image: [
> > ]]components-pom-1.0.2-20120519.090019-2.pom<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-2.pom
> >20-May-2012
> > 18:1315K [image: [
> > ]]components-pom-1.0.2-20120519.090019-2.pom.md5<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-2.pom.md5
> >20-May-2012
> > 18:1332 [image: [
> > ]]components-pom-1.0.2-20120519.090019-2.pom.sha1<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-2.pom.sha1
> >20-May-2012
> > 18:1340 [image: [
> > ]]components-pom-1.0.2-20120519.090019-3.pom<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-3.pom
> >20-May-2012
> > 18:1415K [image: [
> > ]]components-pom-1.0.2-20120519.090019-3.pom.md5<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-3.pom.md5
> >20-May-2012
> > 18:1432 [image: [
> > ]]components-pom-1.0.2-20120519.090019-3.pom.sha1<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-3.pom.sha1
> >20-May-2012
> > 18:1440 [image: [
> > ]]components-pom-1.0.2-20120519.090019-4.pom<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-4.pom
> >21-May-2012
> > 05:0015K [image: [
> > ]]components-pom-1.0.2-20120519.090019-4.pom.md5<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-4.pom.md5
> >21-May-2012
> > 05:0032 [image: [
> > ]]components-pom-1.0.2-20120519.090019-4.pom.sha1<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/components-pom-1.0.2-20120519.090019-4.pom.sha1
> >21-May-2012
> > 05:0040 [image: [
> > ]]maven-metadata.xml<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/maven-metadata.xml
> >21-May-2012
> > 05:00374 [image: [
> > ]]maven-metadata.xml.md5<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/maven-metadata.xml.md5
> >21-May-2012
> > 05:0032 [image: [
> > ]]maven-metadata.xml.sha1<
> http://www.neoarcane.com/maven/repository/com/neoarcane/components/components-pom/1.0.2-SNAPSHOT/maven-metadata.xml.sha1
> >21-May-2012
> > 05:0040
> >
> > any ideas on how I clean this up so I can test with my -SNAPSHOT and
> don't
> > have to release on every code change?
> >
> > Louis
> >
> > --
> > Dr. Louis Smith, ThD
> > Chief Technology Officer, Kyra InfoTech
> > Engineer-in-Training, Veteran's Memorial Railroad
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
>


-- 
Dr. Louis Smith, ThD
Chief Technology Officer, Kyra InfoTech
Colonel, Commemorative Air Force

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message