Re: maven sql plugin and clobs

2010-12-23 Thread Mark Struberg
How did you generate/create the clob script?

I'm using clobs in mysql migrationdata imports and they work fine. I'm using 
mysqldump to create the sql file which correctly escapes those values.

I assume you have Oracle 11? (up 2 Oracle 10 it was imo only able to export to 
their own bin format)


LieGrue,
strub

--- On Wed, 12/22/10, Jason Perry jpe...@brightcove.com wrote:

 From: Jason Perry jpe...@brightcove.com
 Subject: maven sql plugin and clobs
 To: users@maven.apache.org
 Date: Wednesday, December 22, 2010, 8:38 PM
 Hi,
 
 I am running into a problem when trying trying to import a
 .sql file that
 has clob data.  Anyone run into this or know of a
 workaround?  Here is the
 failure:
 
 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] ORA-06550: line 6, column 15:
 PLS-00103: Encountered the symbol 
 html
 head
 meta http-equiv=Content-Type content=text/htm when
 expecting one of the
 following:
 
    ( - + case mod new not null an
 identifier
    a double-quoted
 delimited-identifier a bind variable avg
    count current exists max min prior sql
 stddev sum variance
    execute forall merge time timestamp
 interval date
    a string literal with character set
 specification
    a number a single-quoted SQL
 string pipe
    an alternatively-quoted string
 literal
 
 Thanks,
     -- Jay
 




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



modifying properties while creating files in archetype

2010-12-23 Thread Dirk Olmes
Hi,

while creating an archetype, file names can be substituted by putting
filenames like __myProperty__Foo.java. This works like a charm but I'd
like to have more control over the properties that are available.
Ideally, I'd like to add more properties programatically while the
archetype is running.

Use case: when creating a new project from the archetype users have to
specify the name of the service they are invoking, e.g. Salesforce. I
would like to generate a file based on the lowercase name of that
service name (e.g. translate Salesforce to salesforce). Is this
possible?

-dirk

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: metadata.versioning.release entry in maven-metadata.xml file is not updated by Maven 3

2010-12-23 Thread Benjamin Bentmann

Marcin Kuthan wrote:


http://code.google.com/p/m4enterprise/source/browse/snapshot-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=770
The last revision 770 is a result of deploying 1.3-SNAPSHOT by Maven 2

Only in the last case, when Maven 2 was used for deployment, element
metadata.versioning.release is defined.


A snapshot is not a release and that Maven 2.x happily marks a snapshot 
as such is a bug.



Could you tell me where I can find the official reference for
maven-metadata format? Has it been changed since Maven 2.x?


http://maven.apache.org/ref/3.0.1/maven-repository-metadata/repository-metadata.html


Benjamin

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: metadata.versioning.release entry in maven-metadata.xml file is not updated by Maven 3

2010-12-23 Thread Marcin Kuthan
Thanks for the link to the metadata reference.

I just checked again for released versions. First I cleaned up local
repository and remote repositories as well.

After 1.0 deployment latest release version has been updated:
http://code.google.com/p/m4enterprise/source/browse/release-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=798

After 1.1 deployment latest release version has not been updated:
http://code.google.com/p/m4enterprise/source/browse/release-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=806

When I switched back to Maven 2, latest release version has been updated:
http://code.google.com/p/m4enterprise/source/browse/release-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=814

After metadata reference lecture I checked again snapshot deployment:
http://code.google.com/p/m4enterprise/source/browse/snapshot-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=826
(Maven2)
http://code.google.com/p/m4enterprise/source/browse/snapshot-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=837
(Maven2)
http://code.google.com/p/m4enterprise/source/browse/snapshot-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=845
(Maven3)

From the reference documentation:
latest  What the latest version in the directory is, including snapshots
release What the latest version in the directory is, of the releases
snapshotThe current snapshot data in use for this version
versions/version*   (Many) Versions available for the artifact
lastUpdated When the metadata was last updated
snapshotVersions/snapshotVersion*   (Many) The snapshot versions
available for the artifact.

It looks that latest, snapshot and snapshotVersions elements are
not used at all. And release and versions elements are used
incorrectly.

Thanks,
Marcin

On 23 December 2010 12:06, Benjamin Bentmann benjamin.bentm...@udo.edu wrote:
 Marcin Kuthan wrote:


 http://code.google.com/p/m4enterprise/source/browse/snapshot-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=770
 The last revision 770 is a result of deploying 1.3-SNAPSHOT by Maven 2

 Only in the last case, when Maven 2 was used for deployment, element
 metadata.versioning.release is defined.

 A snapshot is not a release and that Maven 2.x happily marks a snapshot as
 such is a bug.

 Could you tell me where I can find the official reference for
 maven-metadata format? Has it been changed since Maven 2.x?

 http://maven.apache.org/ref/3.0.1/maven-repository-metadata/repository-metadata.html


 Benjamin

 -
 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: metadata.versioning.release entry in maven-metadata.xml file is not updated by Maven 3

2010-12-23 Thread Benjamin Bentmann

Marcin Kuthan wrote:


After 1.1 deployment latest release version has not been updated:
http://code.google.com/p/m4enterprise/source/browse/release-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=806


Good catch, filled as http://jira.codehaus.org/browse/MNG-4952.


Benjamin

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: metadata.versioning.release entry in maven-metadata.xml file is not updated by Maven 3

2010-12-23 Thread Marcin Kuthan
Thanks Benjamin. I will keep the artifacts in the repository for reference.

Marcin

On 23 December 2010 13:22, Benjamin Bentmann benjamin.bentm...@udo.edu wrote:
 Marcin Kuthan wrote:

 After 1.1 deployment latest release version has not been updated:

 http://code.google.com/p/m4enterprise/source/browse/release-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=806

 Good catch, filled as http://jira.codehaus.org/browse/MNG-4952.


 Benjamin

 -
 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



maven-war-plugin overlay versus just plain using the dependency plugin

2010-12-23 Thread Benson Margulies
I confess that I've got myself somewhat turned around about the war
plugin and overlays versus unpacked wars.

I have some tests that run against the the 'unpacked' war, so I need
the things that would come through overlay to be there. The overlay
things are NOT wars at all, they are just miscellaneous data files. So
one might think that it would make more sense to use the dependency
plugin -- but I'm not sure where to put it in the life cycle so that
the war plugin will correctly sweep up its output.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Support for the current jetty-maven-plugin

2010-12-23 Thread Nathan Wilhelmi
Hi - Anyone know where to find support lists for the jetty plugin?

Thanks!



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Build Numbering and Labelling

2010-12-23 Thread Eric Fetzer
I'll hit the continuum list, thanks!



On Dec 22, 2010, at 2:53 PM, Yanko, Curtis curt_ya...@uhc.com wrote:

 We use our build management system for these items. We read a version number 
 out of the POM to create a fully qualified version in the BMS and then pass 
 that back into Maven for inclusion in manifest and such.
 
 Labeling is definitely the responsibility of the BMS too.
 
 
 
 Curt Yanko | Continuous Integration Services | UnitedHealth Group IT 
 Making IT Happen, one build at a time, 600 times a day
 
 
 -Original Message-
 From: Eric Fetzer [mailto:elstonk...@yahoo.com] 
 Sent: Wednesday, December 22, 2010 12:47 PM
 To: Maven Users List
 Subject: Build Numbering and Labelling
 
 I'm pretty new to maven and wondering if there are any 
 magical plugins in maven to increment digits of a build 
 number, snap a label in scm (I saw scm:tag, but was thinking 
 along the lines of a View label rather than Revision label in 
 StarTeam).  If not, no biggie, I can go along the lines of 
 using a build.number properties file and doing the math and 
 such in the build file like I do in Ant, but thought there 
 might be a cheat already out there.
 
 Thanks,
 Eric
 
 
 
 
 
 This e-mail, including attachments, may include confidential and/or
 proprietary information, and may be used only by the person or entity
 to which it is addressed. If the reader of this e-mail is not the intended
 recipient or his or her authorized agent, the reader is hereby notified
 that any dissemination, distribution or copying of this e-mail is
 prohibited. If you have received this e-mail in error, please notify the
 sender by replying to this message and delete this e-mail immediately.
 
 
 -
 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: Problem with classpath for tests

2010-12-23 Thread Asmann, Roland
The problem here is that Hibernate doesn't scan my EntityBeans/doesn't 
find any annotations on them. This in turn means that my DB isn't 
initialized and my tests can't run!

Isn't there anybody out there that has had this problem after the 
classpath-change?



On 20.12.2010 14:49, Asmann, Roland wrote:
 Sorry, I got the location of the directories wrong... They were last but
 are now first!


 On 20.12.2010 14:47, Asmann, Roland wrote:
   Hi all,
  
   I've been trying to get some projects running on my Hudson server, abd
   am running into problems. I've hunted down the problem to being the
   version of Maven that I use!
  
   On my Hudson I am running both 2.0.10 (for some older projects) and
   2.2.1. On both these versions I have a project that is failing.
  
   Now, I asked the developer and he told me he is on Maven 2.0.9... When I
   run with that version, everything works as it should!
  
   From the output generated by Maven, I can see that there is a
   difference in the classpath for the tests. It appears that starting with
   2.0.10, the 'target/classes' and 'target/test-classes' are no longer the
   first entries on the classpath, but the last.
   This seems to be the problem I'm having, and tbh I have no idea on how I
   could fix this problem and get my tests running again... Does anybody
   have an idea or suggestion on how to fix this?
  
   Thanks!
  
   --
   Roland Asmann
   Senior Software Engineer
  
   adesso Austria GmbH
   Floridotower 26. Stock T +43 1 2198790-27
   Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
   A-1210 Wien M +43 664 88657566
   E roland.asm...@adesso.at
   W www.adesso.at
  
   -
business. people. technology. 
   -
  
   -
   To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
   For additional commands, e-mail: users-h...@maven.apache.org
  

 --
 Roland Asmann
 Senior Software Engineer

 adesso Austria GmbH
 Floridotower 26. Stock T +43 1 2198790-27
 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
 A-1210 Wien M +43 664 88657566
 E roland.asm...@adesso.at
 W www.adesso.at

 -
   business. people. technology. 
 -

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


-- 
Roland Asmann
Senior Software Engineer

adesso Austria GmbH
Floridotower 26. Stock  T +43 1 2198790-27
Floridsdorfer Hauptstr. 1   F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asm...@adesso.at
W www.adesso.at

-
  business. people. technology. 
-

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



release plugin versus dependency plugin

2010-12-23 Thread Benson Margulies
Under a single aggregate project, I have two projects.

Project 1 builds an extra artifact with a classifier.

Project 2 uses dependency:unpack to unpack it for inclusion in a, yes,
larger artifact.

All's well until I try to run the release:prepare goal, at which
point, the first artifact is missing when the second project asks for
it.

any ideas? Why is the :prepare run different?


[INFO] Embedded error: Unable to download the artifact from any repository
[INFO]
[INFO] Try downloading the file manually from the project website.
[INFO]
[INFO] Then, install it using the command:
[INFO] mvn install:install-file -DgroupId=com.basistech.jug
-DartifactId=rlp-gate-plugin -Dversion=8 -Dclassifier=gate-plugin
-Dpackaging=zip -Dfile=/path/to/file
[INFO]
[INFO] Alternatively, if you host your own repository you can deploy
the file there:
[INFO] mvn deploy:deploy-file -DgroupId=com.basistech.jug
-DartifactId=rlp-gate-plugin -Dversion=8 -Dclassifier=gate-plugin
-Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[INFO]
[INFO]
[INFO]   com.basistech.jug:rlp-gate-plugin:zip:8

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: release plugin versus dependency plugin

2010-12-23 Thread Mark Struberg
Hi Benson!

Please check the preparationGoals property in the release plugin [1]

Maybe you Please try with something like -DpreparationGoals=clean install


LieGrue,
strub

[1] 
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#preparationGoals


--- On Thu, 12/23/10, Benson Margulies bimargul...@gmail.com wrote:

 From: Benson Margulies bimargul...@gmail.com
 Subject: release plugin versus dependency plugin
 To: Maven Users List users@maven.apache.org
 Date: Thursday, December 23, 2010, 6:17 PM
 Under a single aggregate project, I
 have two projects.
 
 Project 1 builds an extra artifact with a classifier.
 
 Project 2 uses dependency:unpack to unpack it for inclusion
 in a, yes,
 larger artifact.
 
 All's well until I try to run the release:prepare goal, at
 which
 point, the first artifact is missing when the second
 project asks for
 it.
 
 any ideas? Why is the :prepare run different?
 
 
 [INFO] Embedded error: Unable to download the artifact from
 any repository
 [INFO]
 [INFO] Try downloading the file manually from the project
 website.
 [INFO]
 [INFO] Then, install it using the command:
 [INFO]     mvn install:install-file
 -DgroupId=com.basistech.jug
 -DartifactId=rlp-gate-plugin -Dversion=8
 -Dclassifier=gate-plugin
 -Dpackaging=zip -Dfile=/path/to/file
 [INFO]
 [INFO] Alternatively, if you host your own repository you
 can deploy
 the file there:
 [INFO]     mvn deploy:deploy-file
 -DgroupId=com.basistech.jug
 -DartifactId=rlp-gate-plugin -Dversion=8
 -Dclassifier=gate-plugin
 -Dpackaging=zip -Dfile=/path/to/file -Durl=[url]
 -DrepositoryId=[id]
 [INFO]
 [INFO]
 [INFO]   com.basistech.jug:rlp-gate-plugin:zip:8
 
 -
 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