Re: hibernate3-maven-plugin hbm2ddl always try to connect
Dňa Pi 9. Február 2007 Johann Reyes napísal: > Hello Miso > > Try this: > > > org.codehaus.mojo > hibernate3-maven-plugin > 2.0-SNAPSHOT > > > > hbm2ddl > > configuration > > > > schema.sql > > > > hello Johann, without changes... still connecting to database... m. smime.p7s Description: S/MIME cryptographic signature
Re: How to stop a hung build
Is it 1.0.3? If so and restarting Continuum and doing a build all didn't work you can modify the project state in the database with an SQL client like squirrel. On 2/9/07, Enrique Gaona <[EMAIL PROTECTED]> wrote: Hi, I have a build that terminated after 17 mins due to an error, but continuum still thinks the project is still building. The elapse time is now showing over 2 hours and continues to increment even though the build only ran for 17mins. Is there a way I can reset the DB? I've tried restarting continuum to no avail.Any help is very much appreciated. Enrique -- Adam Altemus Software Engineer, MobilVox http://www.mobilvox.com [EMAIL PROTECTED] Home e-mail [EMAIL PROTECTED]
Re: giving -Dpde=true to eclipse:eclipse doesn't work
> Steinar Bang <[EMAIL PROTECTED]>: >>> Platform: Intel Pentium M, Ubuntu Dapper, >>> Sun Java 2 SDK 1.6.0_06, >>> maven 2.0.4, >>> maven-eclipse-plugin 2.3 [snip!] > But, of course, I'm not all there yet. Because right now, I have a > bunch of META-INF/MANIFEST.MF files containing nothing but > Bundle-Classpath. And I need a bit more to make these projects play > as plug-ins. At least: > - Bundle-Symbolic-Name > - Bundle-Version > Possibly: > - Export-Package > - Import-Package > - Bundle-Activator > That information is currently residing in the POMs as > for maven-jar-plugin. Duplicating it manually > into the MANIFEST.MF files, seems like a bad idea. As an experiment I unpacked the META-INF/MANIFEST.MF files from the projects' bundle incarnations. And I still can't get it to work. I think it's a class-path issue. The projects have, in their POMs, elements referring other OSGi bundles, that won't be practical to get into eclipse with eclipse:eclipse and turn into PDE projects, in the workspace. These bundles are put into the bundle-classpath by eclipse:eclipse goal. And the bundles in bundle-classpath doesn't seem to see bundles in the PDE target platform. The bundles also exists in the PDE target platform, but eclipse:eclipse has no way of knowing that (no way of knowing the bundle-symboliic-name/version-no tuple from the groupId/artifactId/version-no tuple in the dependency... I don't know if it tries, but if it did try, it would probably use artifactId/version-no (that would be consistent with eg. the .project file generated by eclipse:eclipse), and the bundles in question are using groupId/version-no). One error message of this kind I see, is The project was not built since its build path is incomplete. Cannot find the class file for org.osgi.framework.BundleActivator. Fix the build path then try building this project So... I could probably get rid of the white-on-red-Xes, by using eclipse:make-artifacts to put the eclipse runtime into my local maven repository, and create dependencies to these bundles, and in that way get them into the bundle-classpath. But that seems like a serious hack, and defeating the use of OSGi bundles in the first place. So even if I could resolve the generation of MANIFEST.MF issues, I'm guessing mvn eclipse:eclipse -Declipse.pde=true is a dead end for me...? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to build offline??
Hi, Looks like you are running with snapshots enabled (surefire plugin uses v2.3-SNAPSHOT) - not sure how exactly maven behaves when snapshot versions of plugins are enabled, but it may be that it requires to be online all the time. Regards, Johan Marilyn Sander -X (marilysa - Digital-X, Inc. at Cisco) wrote: > Hi, all. > > I understood that it should be possible to do a Maven build offline, > that is, with no connection to any repository except the local > repository. I understand that all necessary artifacts have to already > be in the local repository. > > In fact, I did this exercise a couple of months ago with great success. > But Maven seems to have changed in the meantime. > > I have a situation where I just did a build using a local repository. > The build succeeded. From that success, I assumed that all necessary > artifacts had been downloaded to the local repository. I then tried to > repeat that build using the "-o" parameter to Maven, using that very > same local repository. The build failed because some artifacts were > missing. I re-ran it with " -o -e " as recommend, but got no additional > information. Can someone explain what is going on? Should I file a JIRA > report? > > I received the messages below. Three artifacts are missing. In all > three cases the pom file and its checksum file are present, but no > corresponding jar file. In the dependency paths to the three jar files, > some of the artifacts have jar files in the local repository and some > have only the pom file.But if the jar files are needed, how could > the original build have run successfully? Also, my repository does not > have dummy:dummy. Can anyone explain what dummy:dummy is? > > I could start downloading things manually, but (a) I thought it should > not be necessary, and (b) I could end up having to download dozens of > things manually, as this is a very large build. > > Thanks for any insights that could be provided. > > --Marilyn Sander > > [exec] Missing: > [exec] -- > [exec] 1) classworlds:classworlds:jar:1.1-alpha-2 > > [exec] Try downloading the file manually from the project > website. > > [exec] Then, install it using the command: > [exec] mvn install:install-file -DgroupId=classworlds > -DartifactId=classworlds \ > [exec] -Dversion=1.1-alpha-2 -Dpackaging=jar > -Dfile=/path/to/file > > [exec] Path to dependency: > [exec] 1) dummy:dummy:jar:1.0 > [exec] 2) > org.apache.maven.surefire:surefire-booter:jar:2.3-SNAPSHOT > [exec] 3) org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7 > [exec] 4) > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 > [exec] 5) classworlds:classworlds:jar:1.1-alpha-2 > > [exec] 2) > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 > > [exec] Try downloading the file manually from the project > website. > > [exec] Then, install it using the command: > [exec] mvn install:install-file -DgroupId=org.codehaus.plexus > -DartifactId=plexus-container-default \ > [exec] -Dversion=1.0-alpha-8 -Dpackaging=jar > -Dfile=/path/to/file > > [exec] Path to dependency: > [exec] 1) dummy:dummy:jar:1.0 > [exec] 2) > org.apache.maven.surefire:surefire-booter:jar:2.3-SNAPSHOT > [exec] 3) org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7 > [exec] 4) > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 > > [exec] 3) org.codehaus.plexus:plexus-utils:jar:1.1 > > [exec] Try downloading the file manually from the project > website. > > [exec] Then, install it using the command: > [exec] mvn install:install-file -DgroupId=org.codehaus.plexus > -DartifactId=plexus-utils \ > [exec] -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file > > [exec] Path to dependency: > [exec] 1) dummy:dummy:jar:1.0 > [exec] 2) > org.apache.maven.surefire:surefire-booter:jar:2.3-SNAPSHOT > [exec] 3) org.codehaus.plexus:plexus-utils:jar:1.1 > > [exec] -- > [exec] 3 required artifacts are missing. > [exec] for artifact: > [exec] dummy:dummy:jar:1.0 > > [exec] from the specified remote repositories: > [exec] central (http://maven.cisco.com/maven-proxy/repository), > [exec] bounty-build-proxy > (http://bounty-build.cisco.com/maven-proxy/repository) > > > [exec] NOTE: Maven is executing in offline mode. Any artifacts not > already in your local > [exec] repository will be inaccessible. > > > > -- you too? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.1 timeline?
Hi, On 2/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Sorry if this has been asked, but any idea when Maven 2.1 will be release? I'm running into the site + jxr problem (http://jira.codehaus.org/browse/MSITE-138) which won't be fixed in the 2.0.x branch. I don't understand. It's a plugin issue and it's fixed (see MISTE-138). You can rebuild the site plugin from trunk, it has nothing to do with a Maven distribution release. Cheers, Stéphane Regards, Brian Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: giving -Dpde=true to eclipse:eclipse doesn't work
> Steinar Bang <[EMAIL PROTECTED]>: > Steinar Bang <[EMAIL PROTECTED]>: >> Platform: Intel Pentium M, Ubuntu Dapper, >> Sun Java 2 SDK 1.6.0_06, >> maven 2.0.4, >> maven-eclipse-plugin 2.3 [snip!] >> Ie. there is no plugin nature in .project, and .classpath still refers >> to files directly in the local maven repository. > After the parameter name correction the .project and .classpath looks > correct. But no jars are copied to a project local directory, like > the documentation says it should be. > http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html What happened, was that there was no META-INF/MANIFEST.MF in the project directories, and that I got the following warning [WARNING] The references manifest file doesn't exist, plugin dependencies will not be updated: /media/sda8/bangste/p4/depot/ccr/MAIN/com.fastsearch.ccr.repository.repositorydef/META-INF/MANIFEST.MF I created the META-INF directories, containing empty MANIFEST.MF files, and then had a bit more success. Ie. the jars weren't copied, but they were made in the .project file (I'm not sure what that means wrt. creating an RCP application containing these plugin projects...?) But, of course, I'm not all there yet. Because right now, I have a bunch of META-INF/MANIFEST.MF files containing nothing but Bundle-Classpath. And I need a bit more to make these projects play as plug-ins. At least: - Bundle-Symbolic-Name - Bundle-Version Possibly: - Export-Package - Import-Package - Bundle-Activator That information is currently residing in the POMs as for maven-jar-plugin. Duplicating it manually into the MANIFEST.MF files, seems like a bad idea. Any suggestions for automating this? Thanx! - Steinar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
