Re: import project into Eclipse 3.4
If you're just trying to import it into Eclipse, then you should just create an Enterprise ear project and a Dynamic Web Project and add the source code to the Dynamic Web Project. Make sure you select your compiler and that you add the Dynamic Web Project. Or, maybe the configuration files for Eclipse that seem to be already present (the .classpath is a tell) will work if you just import the project into Eclipse? Either way, importing into Eclipse by setting up a Maven project is a long way around. If you had a valid Maven project structure, then you'd just run mvn eclipse:eclipse and it would generate working Eclipse project descriptors (the .classpath/.project I just mentioned) ear/war configuration that you could then use to import into Eclipse. Sorry if this doesn't answer the question entirely, but hopefully it will be insightful. Thanks, Josh On Sat, Aug 23, 2008 at 6:53 AM, sam wun [EMAIL PROTECTED] wrote: HI, I downloaded a sample project eg. com.eclipsedistilled.catalog in my c:\DEV\samples\ directory. eg. c:\DEV\samples\com.eclipsedistilled.cataglog c:\DEV\samples\com.eclipsedistilled.cataglog\bin c:\DEV\samples\com.eclipsedistilled.cataglog\src c:\DEV\samples\com.eclipsedistilled.cataglog\.classpath c:\DEV\samples\com.eclipsedistilled.cataglog\.cvsignore c:\DEV\samples\com.eclipsedistilled.cataglog\.project I heard that we have to use maven to create a project (war / ear) file in order to import it into eclipse. What is the procedure/steps to do that? Thanks -- Joshua Long Sun Certified Java Programmer http://www.joshlong.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Making the case for Maven to managment
Hi everyone, I'm trying to make a case for Maven and I'm going to need to provide a better reason than it's better than a kick in the face! to managment. I'm at a bank, so everything is subject to heavy scrutiny. Essentially, our project hardly compiles and is so untestable that upon check out no less than 5 files need to change to get it to the point where we can compile it (once we've created a working project in either IntelliJ or Eclipse, which has hitherto never been too successful. Some of us just ant deploy every change instead of iteratively deploying using our IDE's weblogic facilities. So basically, I know I could solve the file issues with Maven profiles. I know that using the Maven site plugin and reports like PMD and JUnit and so on I could provide great dashboard like functionality into our application. I know that I can solve the broken project descriptors, too. All with Maven, but strictly speaking these are technically still process enhancements, which come down as a liability. In terms of shear resource hours, I should imagine 10 hours or so to get our two projects moved over and acheive parity with our current Ant script and even perhaps to solve all the Eclipse/IntelliJ nonsense and get decent, default mvn site generation, and to change our existing production support script which is Ant to interface with the ant script Maven will generate for us. Basically, it won't take a lot. But that's not enough. How do I make this case in the face of so hostile a mentality? Have you ever had to make the case? Any insight on how to move forward would be appreciated. Thanks, Joshua Long Sun Certified Java Programmer http://www.joshlong.com/
A few issues for which it's not worth inundating the list multiple times. Help appreciated
Hi all, I am working to convert a project and need to provide: - ClearCase Issue Management integration / reporting - Eclipse project descriptor generation for Workshop (this is the latest version of Oracle Workshop, but it's still Eclipse 3.1 under the hood (I think)! - It's not likely I'll get permission to setup an internal LAN repository, so I need to be able to setup a file:// based repository and (blech) check in the jars (as they'd lie in the repository) into CVS. Has anyone done this? Any good, bad (I already see the ugly!)? - Finally, has any one done security checks with Fortify? And if so, have you integrated it with Maven? I can't seem to find a plugin a la PMD/ FindBugz' integrations. I know there's an Ant task, has any one used that via Maven? Thanks all, Josh Long http://www.joshlong.com
WTP, Eclipse, and Maven with APP-INF/lib
Hello I have an ear which in turn has dependencies that need to be furnished to all sub projects (a few EJBs, a few WARs). The maven build itself is configured to do the right thing and, in the resulting .ear, yeilds an APP-INF/lib director with all non ejb/war/car dependencies. I can even run mvn eclipse:eclipse with the wtp support and get a pretty useful setup inside of eclipse. I also setup maven to not generate -SNAPSHOT-1.0.jar on the artifacts, which makes the application.xml something we can keep in source. This in turn makes eclipse happy because it can let us use the WTP facilities for an EAR. However, when we take the ear project and add it to a server (JBoss), and then publish that eclipse project, eclipse builds an ear (amazingly !) that works just like if mvn had built it EXCEPT for /APP-INF/lib/*jar at the root of the ear project. Apparently this has something to do with the EAR Libraries library, but I'm unsure of how to accomodate this. Plus, it ideally should be correctly configured by the mavne plugin. Does anyone have any way around this? A custom mojo I might bind to the eclipse:eclipse phase? Insight on how this would be configured in the low level eclipse .settings stufff? Anything at all would be appreciated. Thanks, Josh Long - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse 3.3 natures/builders and maven
Hi all Does anyone have any advice / feedback on getting mvn eclipse:eclipse to work well enough so that an ear pom, ejb pom, and a war pom are all assigned the correct eclipse natures / builders when the descriptors are built? Thanks! Josh Long - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is it possible ot sign the jar with all dependencies that maven generates using its assembly plugin? any help appreciated.
Hello list, Is it possible ot sign the jar with all dependencies that maven generates using its assembly plugin? The maven jar plugin has manifest and keystore config params. Are those accessible or usable osmehow by the assembly plugin? Scenario: I'm trying to deploy a large jar with all dependencies a)signed and b) included in the main jar Any help appreciated, of course. Thanks, Joshua
Re: What's the easiest way to deploy an existing project to a different server?
THATS IT?? good news. Thanks again, Tom. Forgive my novice question. Josh On 11/18/06, Tom Huybrechts [EMAIL PROTECTED] wrote: Use an alternate deployment repository: mvn deploy -DaltDeploymentRepository=myrepo::default::myurl See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html On 11/17/06, Josh Long [EMAIL PROTECTED] wrote: I wuld like to deploy an open source project that publishes dependencies and has source code available to my repository. The project uses maven 2, and I use maven 2. When I invoke maven deploy, maven gleefully attempts to deploy it to the projects repository and then fails (naturally) as it can't authenticate. I don't want to have to (as I tend to svn update their code frequently) modify their pom to configure a second repository/server. what's the best way to introduce a seperate server into the deployment process without really touching their code? Thanks, Josh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What's the easiest way to deploy an existing project to a different server?
I wuld like to deploy an open source project that publishes dependencies and has source code available to my repository. The project uses maven 2, and I use maven 2. When I invoke maven deploy, maven gleefully attempts to deploy it to the projects repository and then fails (naturally) as it can't authenticate. I don't want to have to (as I tend to svn update their code frequently) modify their pom to configure a second repository/server. what's the best way to introduce a seperate server into the deployment process without really touching their code? Thanks, Josh
Re: Maven rant
+1 this is a fantastic idea.. would it take the form of an elaboration on the mvn site plugin? I propose that, at the lowest level, a test asserting that javadoc containing more than the default @author and @return tags in the javadoc for methods that arent property accessor/mutators would ensure most code is documented. then, if the test is met, the javadocs can be considered 'present'. Naturally there are any number of other tests... This would be the easiest level of compliance with the edict ( all code must be documented). Naturally, the site generated for the artifact woud provide the higher level overivew of the code thats much needed when diving into something... I propose perhaps a new type of doc format could be created / employed by the site plugin. src/site/wiki, or somehting like that. this would be content that once processed by the plugin would be entered into a known wikis (configurable in the pom) database which itself is editable/annotatable.. somehow the docs might be synced with this wiki.. or something... This would allow the structure of the wiki/documentation to spring forth from the code and the developers where the knowledge is cached. it would also allow coupling/interaction between the javadocs/reports and the documentation. But once that basic structure is set up, it would easily migrate to an interactive community driven format. the wiki would facilitate comments. the plugin might even read the wiki db and restore the comments into the documentation or something... These are all just proposals, as I wonder what this sort of solution might look like. Josh On 11/3/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: +1 This would make it even possible to create a user/project dedicated manuals. The project pom-file already has all plugins being used by the project. The generated manual will then just include the docs for these plugins and use the actual plugin version. Regards, Minto -Oorspronkelijk bericht- Van: Gisbert Amm [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 3 november 2006 9:43 Aan: Maven Users List Onderwerp: Re: Maven rant Why not use the central repo for documentation aswell? E.g. in http://www.ibiblio.org/maven2/plugins/org/apache/maven/plugins/maven-ant-plugin/2.0-alpha-2/ could exist a bundle named user-manual.zip, containing the sources for the user-manual. There could be a reference-manual.zip, a developers-manual.zip and so on. The Wiki pages could be generated out of these sources. One step of the release process of a plugin (or the Maven core) would be to integrate possible user comments from the wiki into the documentation sources and regenerate the respective wiki pages. A Maven plugin could be written to download all document sources of a certain category, bring them into a reasonable order (defined by models within the plugin), add introductionary material from common bundles, table of contents, indexes etc. and produce a users manual, reference manual and so on in a format the user can choose (HTML, PDF ...) Even the Maven website could be produced by such a plugin; it would just be defined by another documentation model. Just applying the same principles used for software production to documentation ... I hope I was able to make myself understood (sorry for my English) and am not dreaming too far into the blue ... -Gisbert Gregory Kick wrote: Ok, this is think outside the box time... I like Thomas' comments on centralizing documentation. I really, really like Thomas' comments on centralizing documentation. However, I think the logistics may be off. I'm thinking of the documentation problem as similar to the build problem. Before there was maven, users had to go from site to site downloading jars and collecting them into a useful, coherent code base every time they wanted to build because a bunch of different groups contributed a bunch of small, but useful artifacts. That got fixed. Unfortunately, we're now finding that users are going from site to site browsing documentation and collecting it into a useful, coherent knowledge base every time they want to understand something because a bunch of different groups contributed a bunch of small, but useful bits of documentation. So, here's what I propose: Lets create a repository for documentation. The docs will exist within the projects, as they do now, and we'll use an APT/Wiki hybrid that allows for linking between projects (e.g. [[groupId:artifactID]]) and documents (e.g. guides, javadocs, etc.) within those projects. That way, there's quality control because the docs have to be committed, we avoid the unrealistic make-a-giant-book-that-somebody's-going-to-be-in-charge-of-because-I-d on't-want-to plan, and we get the centralized feel with out having to duplicate the little bits of usefulness that already exist. Obviously, there will be a lot of gaps, broken links, etc. in the early stages, but I don't think that it would be any worse
Re: maven site into Trac?
The clamoring masses have it.. please release it On 7/30/06, Srepfler Srgjan [EMAIL PROTECTED] wrote: YES! :) Srgjan Andrew Williams wrote: :) I am the dev behind dev.rectang.com and can tell you it is not manually done :) I have a trac plugin that is almost ready for a release that does it for me. step 1) install plugin, tell it where the site is generated to (on the filesystem) step 2) set your site to use the maven-trac-skin (or whatever I call it when it is released) and deploy it into the expected area. Shall I announce here when it is ready perhaps? Andrew Valerio Schiavoni wrote: hello everyone, any one knows how to 'merge' the maven generated website within Trac, as it's done here: http://dev.rectang.com/projects/javautil/maven/ i think they did it 'manually'..but maybe not. thanks, valerio - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spring 2.0, hibernate/ejb 3
Ah so.. i'll have a whack at that, thank you both so much! Josh On 7/17/06, Markus Wolf [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hibernate annotations have a dependency on the javax.persistence jar, which of course isn available but i got the correct iteration (the one shipped in hibernate-annotations' lib dir for 3.0beta2 and placed it in my private repository.. so that works wonderfully. im not faring sowell at trying to get spring 2.0m4 to work, though.. any one else have any luck here? The javax.persistence final release is available in the java.net repository here: repository idjava-net/id namejava.net repository/name !-- NOTE: this URL must be HTTPS. However, unfortunately this doesn't work behind a firewall. See: http://jira.codehaus.org/browse/WAGONHTTP-6 ... for the source of that problem. Users behind firewalls will have to manually download the files from this repository and transfer them to their local repository. y -- url https://maven-repository.dev.java.net/nonav/repository /url layoutlegacy/layout snapshots enabledfalse/enabled /snapshots /repository Markus Wolf - -- __ Markus Wolf Wedeler Landstrasse 63 22559 Hamburg tel: (+49) 40 / 550 083 70 mob: (+49) 177 / 288 48 67 web: http://www.matrixweb.de icq: #109622365 pgp: http://wwwkeys.de.pgp.net __ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEu0t5YuGbqyQxpHcRAjZ4AJ9lrg1Y4f/2jvzu2bd/p+AJEiz6YwCfV4MR HloWHQR3xkMzaKwdp3pwkwQ= =q1VR -END PGP SIGNATURE- - 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]
Spring 2.0, hibernate/ejb 3
Has anyone gotten the latest (or something close to a 2.0 release, and not 1.2.6) iteration of Spring, Hibernate 3 and ejb/hibrnate annotations to work? if so, what would the pom for that look like? My salient points on my old POM looks like this: dependency groupIdorg.springframework/groupId artifactIdspring-core/artifactId version1.2.7/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring/artifactId version1.2.7/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-dao/artifactId version1.2.7/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.0.5/version optionaltrue/optional /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-annotations/artifactId version3.0beta2/version /dependency Hibernate annotations have a dependency on the javax.persistence jar, which of course isn available but i got the correct iteration (the one shipped in hibernate-annotations' lib dir for 3.0beta2 and placed it in my private repository.. so that works wonderfully. im not faring sowell at trying to get spring 2.0m4 to work, though.. any one else have any luck here? Thanks, Josh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
