Making a Jar for a launchable Swing app
Hey all, a few questions. I'm trying to build a swing application that I can launch from java -jar. Setting Main-Class is pretty well documented from my googling. However, including .properties and a few other important file types (some groovy scripts) is troublesome. If I add any sort of includes directive under build plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration includes... All my .classes disappear from the jar. Additionally, I'd like to add in all the jars from my dependencies. I could find instructions for the assembly plugin, but nothing similar for the jar plugin. How do I go about this? Thanks in advance! -ls -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Making a Jar for a launchable Swing app
Thanks for the quick response. I tried it, but I couldn't figure out how to: 1. Get my .class files in there either. 2. Set up the manifest. Here's what I've got so far: assembly iddist/id includeBaseDirectoryfalse/includeBaseDirectory formats formatjar/format /formats fileSets fileSet directorytarget/classes/directory outputDirectory/outputDirectory includes include*.class/include /includes /fileSet fileSet directorysrc/main/scripts/directory outputDirectoryscripts/outputDirectory includes include*.groovy/include /includes /fileSet fileSet directorysrc/main/java/directory outputDirectory/outputDirectory includes include**/*.properties/include /includes /fileSet /fileSets /assembly Any ideas? On Mon, Apr 14, 2008 at 3:21 PM, Wayne Fay [EMAIL PROTECTED] wrote: You should just use the assembly plugin directly. It can produce jars and was really created for this kind of use case. You might want to think about shading the dependency classes, too. Wayne On 4/14/08, Lally Singh [EMAIL PROTECTED] wrote: Hey all, a few questions. I'm trying to build a swing application that I can launch from java -jar. Setting Main-Class is pretty well documented from my googling. However, including .properties and a few other important file types (some groovy scripts) is troublesome. If I add any sort of includes directive under build plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration includes... All my .classes disappear from the jar. Additionally, I'd like to add in all the jars from my dependencies. I could find instructions for the assembly plugin, but nothing similar for the jar plugin. How do I go about this? Thanks in advance! -ls -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - 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] -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Making a Jar for a launchable Swing app
packageNameedu.vt.iddl.mobileadmin/packageName
addClasspathtrue/addClasspath
/manifest
manifestEntries
modedevelopment/mode
url${pom.url}/url
/manifestEntries
/archive
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-2/version
configuration
descriptors
descriptor${basedir}/src/main/assemblies/dist.xml/descriptor
/descriptors
archive
manifest
mainClassedu.vt.iddl.mobileadmin.MobileAdminApp/mainClass
packageNameedu.vt.iddl.mobileadmin/packageName
addClasspathtrue/addClasspath
/manifest
/archive
/configuration
/plugin
/plugins
/build
/project
The assembly file: src/main/assemblies/dist.xml:
?xml version=1.0 encoding=UTF-8?
!--
Document : dist.xml
Created on : April 14, 2008, 1:27 PM
Author : lally
Description:
Sets up the maven assembly plugin to build a proper jar.
--
assembly
iddist/id
includeBaseDirectoryfalse/includeBaseDirectory
formats
formatjar/format
/formats
dependencySets
dependencySet
outputDirectory/outputDirectory
outputFileNameMapping/outputFileNameMapping
unpacktrue/unpack
scoperuntime/scope
/dependencySet
/dependencySets
fileSets
fileSet
directorytarget/classes/directory
outputDirectory/outputDirectory
/fileSet
fileSet
directorysrc/main/scripts/directory
outputDirectoryscripts/outputDirectory
includes
include*.groovy/include
/includes
/fileSet
fileSet
directorysrc/main/java/directory
outputDirectory/outputDirectory
includes
include**/*.properties/include
/includes
/fileSet
fileSet
directorysrc/main/java/directory
outputDirectory/outputDirectory
includes
include**/*.png/include
/includes
/fileSet
/fileSets
/assembly
On Mon, Apr 14, 2008 at 3:27 PM, Manos Batsis
[EMAIL PROTECTED] wrote:
Lally Singh wrote:
Thanks for the quick response. I tried it, but I couldn't figure out how
to:
1. Get my .class files in there either.
2. Set up the manifest.
Here a sample conf we use that tell the plugin to:
1: Put all class files in one jar (including classes from dependencies)
2: Set the main class in the manifest
It's all there if you RTFM ;-)
hth,
Manos
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
!-- you need this to include classes from deps --
descriptorIdjar-with-dependencies/descriptorId
finalNameJAR_NAME_HERE/finalName
outputDirectorytarget//outputDirectory
workDirectorytarget/assembly/work/workDirectory
scoperuntime/scope
archive
manifest
!-- use the following as the main class in the manifest --
mainClassgr.abiss.someproject.App/mainClass
addClasspathtrue/addClasspath
/manifest
/archive
/configuration
executions
execution
idmake-assembly/id
!-- this is used for inheritance merges --
phasepackage/phase
goals
goalattached/goal
/goals
/execution
/executions
/plugin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
H. Lally Singh
Ph.D. Candidate, Computer Science
Virginia Tech
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Making a Jar for a launchable Swing app
Yeah, I follow you. I ended up using the reference info on the jar-with-deps plugin to build the assembly file. The paths are netbeans' default, not mine. Their otherwise-decent tools create them in those places automatically. No point in fighting the system that hard. On Mon, Apr 14, 2008 at 4:13 PM, Wayne Fay [EMAIL PROTECTED] wrote: You should be able to do all of this generally with the jar-with-dependencies configuration in the assembly plugin. Looking at your assembly descriptor, your .groovy, .properties, and .png files should not be in src/main/java but rather src/main/resources. Then they would have been packaged automatically with the rest of the project class files when you allowed Maven to do its normal packaging. Of course, if you have it working now, there's not much reason to keep working on it. But I think there are some non-standard file locations that you are using etc which are the source of some of your problems. Wayne On 4/14/08, Lally Singh [EMAIL PROTECTED] wrote: Thank you too for the quick response. Trust me, I've RTFMd for the last 4 days on this. The documentation is great if you already know what you want to do. If you don't then you spend 4 days digging, pulled along with the feeling that it's as simple as the documentation and experts imply. I got it to work. For the list archives, here's what you do: 1. Use the assembly plugin 2. Create your own descriptor file 3. Copy everything manually. Something I'd hoped wouldn't be necessary, a self-running jar is one of those things I had assumed the toolchain would support easily. Here's my POM. Below that is the assembly file: ?xml version=1.0 encoding=utf-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdedu.vt.iddl.mobile/groupId artifactIdDesktop/artifactId packagingjar/packaging version200801-SNAPSHOT/version nameDesktop/name urlhttp://maven.apache.org/url dependencies dependency groupIdedu.vt.iddl.groovy/groupId artifactIdGroovyBridge/artifactId version200801-SNAPSHOT/version /dependency dependency groupIdorg.codehaus.groovy/groupId artifactIdgroovy-all/artifactId version1.1-beta-3/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdswing/groupId artifactIdappframework/artifactId version1.0.3/version scopecompile/scope /dependency dependency groupIdswing/groupId artifactIdswing-worker/artifactId version1.1/version scopecompile/scope /dependency dependency groupIdnet.java.dev.swing-layout/groupId artifactIdswing-layout/artifactId version1.0.2/version /dependency dependency groupIdcommons-dbcp/groupId artifactIdcommons-dbcp/artifactId version1.2.2/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.14/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring/artifactId version2.5/version /dependency dependency groupIdorg.springframework/groupId artifactIdspring-test/artifactId version2.5/version /dependency /dependencies profiles profile idnetbeans-public/id activation property namenetbeans.execution/name valuetrue/value /property /activation build plugins plugin artifactIdmaven-jar-plugin/artifactId configuration archive manifest addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix mainClassedu.vt.iddl.mobileadmin.MobileAdminApp/mainClass /manifest /archive /configuration /plugin plugin artifactIdmaven-assembly-plugin/artifactId
Re: JUnit, NetBeans 6
I've got this little snippet in my POM:
executions
execution
idtestdata_upload_vto/id
phasetest-compile/phase
goalsgoaloperation/goal/goals
configuration
typeCLEAN_INSERT/type
src${project.basedir}/src/test/data/db_vto.xml/src
urljdbc:mysql://testsql.iddl.vt.edu/vto/url
/configuration
/execution
execution
I get this bit from running my tests in NB:
[groovy:execute {execution: default}]
[ERROR]BUILD ERROR
src/test/data/db_vto.xml (No such file or directory)
For more information, run Maven with the -e switch
I change the file name to db_vtoF.xml in my POM, save the POM,
reloaded the project, and hit test again. The error message referred
to db_vto.xml, not db_vtoF.xml.
Btw, the file's there, and this part of the test process runs fine
from the command line. But in NB, the error shows up. When the right
POM loads, I'll figure out what to put between those ${}.
Thanks,
-ls
On 11/28/07, Milos Kleint [EMAIL PROTECTED] wrote:
what do you mean by old version of POM? netbeans will update the project
definition if you changed the project's own pom, it will not currently do
automatically when changing something in the chain of parent poms. Use the
Reload action on project's popup. However for build execution there is no
caching, what is on disk is always used.
are you using netbeans 5.5 or 6.0? if 6.0, are you using the maven support
from default update center? that one shall open the regular JUnit window if
you run the Test project action. If you use just Build/Rebuild, it shall
underline the errors in output and create a hyperlink to the stacktraces.
Could be a bug.
Milos
On Nov 28, 2007 7:45 PM, Lally Singh [EMAIL PROTECTED] wrote:
Hey all,
I've got a testcase that I'm trying to get working, but I've got a
little dilemma:
- In Netbeans, I can usually get a stacktrace for JUnit errors. But
NB's using a bad (old?) version of my POM. E.g. I changed my pom and
I continue to get an error mesage from the old version. NB's using
some ancient version of my POM (probably from the initial project
import), and I can't get it to use the new version.
- Maven will (obviously) use the latest pom, but I don't know how to
get any sort of failure report from my junit tests. Just a count a
list of the failed tests, but no stack traces or other diagnostics.
Any idea how to fix either/both problems?
Thanks in advance,
-ls
--
H. Lally Singh
Ph.D. Candidate, Computer Science
Virginia Tech
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
H. Lally Singh
Ph.D. Candidate, Computer Science
Virginia Tech
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JUnit, NetBeans 6
Hey all, I've got a testcase that I'm trying to get working, but I've got a little dilemma: - In Netbeans, I can usually get a stacktrace for JUnit errors. But NB's using a bad (old?) version of my POM. E.g. I changed my pom and I continue to get an error mesage from the old version. NB's using some ancient version of my POM (probably from the initial project import), and I can't get it to use the new version. - Maven will (obviously) use the latest pom, but I don't know how to get any sort of failure report from my junit tests. Just a count a list of the failed tests, but no stack traces or other diagnostics. Any idea how to fix either/both problems? Thanks in advance, -ls -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JUnit, NetBeans 6
That fixes my pom problem, but it leaves me in the same state as
before: no JUnit results. The JUnit integration doesn't work with an
external maven.
I just get a pass/fail result, but nothing to tell me why the test
failed (e.g. stack traces).
Is there a way to tell maven to give me more output about what failed
in my tests?
Thanks,
-ls
On 11/28/07, Milos Kleint [EMAIL PROTECTED] wrote:
project.basedir might have been introduced after 2.0.4 (which is what the
embedded maven version is).
http://mevenide.codehaus.org/m2-site/faq.html#question4
or perhaps something to do with groovy plugin? not sure, never tried myself.
please try setting the project to use command line maven for building, that
should make the problem go away. Project/Properties to mark the project as
buildable by command line and Tools/Options for setting the path to maven
itself.
If it's not working then, please file a bug report at
jira.codehaus.org/browse/MEVENIDE
Milos
On Nov 28, 2007 8:00 PM, Lally Singh [EMAIL PROTECTED] wrote:
I've got this little snippet in my POM:
executions
execution
idtestdata_upload_vto/id
phasetest-compile/phase
goalsgoaloperation/goal/goals
configuration
typeCLEAN_INSERT/type
src${project.basedir}/src/test/data/db_vto.xml/src
urljdbc:mysql://testsql.iddl.vt.edu/vto/url
/configuration
/execution
execution
I get this bit from running my tests in NB:
[groovy:execute {execution: default}]
[ERROR]BUILD ERROR
src/test/data/db_vto.xml (No such file or directory)
For more information, run Maven with the -e switch
I change the file name to db_vtoF.xml in my POM, save the POM,
reloaded the project, and hit test again. The error message referred
to db_vto.xml, not db_vtoF.xml.
Btw, the file's there, and this part of the test process runs fine
from the command line. But in NB, the error shows up. When the right
POM loads, I'll figure out what to put between those ${}.
Thanks,
-ls
On 11/28/07, Milos Kleint [EMAIL PROTECTED] wrote:
what do you mean by old version of POM? netbeans will update the project
definition if you changed the project's own pom, it will not currently
do
automatically when changing something in the chain of parent poms. Use
the
Reload action on project's popup. However for build execution there is
no
caching, what is on disk is always used.
are you using netbeans 5.5 or 6.0? if 6.0, are you using the maven
support
from default update center? that one shall open the regular JUnit window
if
you run the Test project action. If you use just Build/Rebuild, it
shall
underline the errors in output and create a hyperlink to the
stacktraces.
Could be a bug.
Milos
On Nov 28, 2007 7:45 PM, Lally Singh [EMAIL PROTECTED] wrote:
Hey all,
I've got a testcase that I'm trying to get working, but I've got a
little dilemma:
- In Netbeans, I can usually get a stacktrace for JUnit errors. But
NB's using a bad (old?) version of my POM. E.g. I changed my pom and
I continue to get an error mesage from the old version. NB's using
some ancient version of my POM (probably from the initial project
import), and I can't get it to use the new version.
- Maven will (obviously) use the latest pom, but I don't know how to
get any sort of failure report from my junit tests. Just a count a
list of the failed tests, but no stack traces or other diagnostics.
Any idea how to fix either/both problems?
Thanks in advance,
-ls
--
H. Lally Singh
Ph.D. Candidate, Computer Science
Virginia Tech
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
H. Lally Singh
Ph.D. Candidate, Computer Science
Virginia Tech
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
H. Lally Singh
Ph.D. Candidate, Computer Science
Virginia Tech
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven's included with Leopard (Mac OS 10.5)
Just fyi: [EMAIL PROTECTED] ~]$ uname -a Darwin hc65210f0.dhcp.vt.edu 9.0.0 Darwin Kernel Version 9.0.0: Tue Oct 9 21:35:55 PDT 2007; root:xnu-1228~1/RELEASE_I386 i386 [EMAIL PROTECTED] ~]$ which mvn /usr/bin/mvn [EMAIL PROTECTED] ~]$ mvn --version Maven version: 2.0.6 [EMAIL PROTECTED] ~]$ I only noticed this when I upgraded and noticed my build failing (I needed 2.0.7 :-) ). Congrats! -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven's included with Leopard (Mac OS 10.5)
On 11/15/07, Graham Leggett [EMAIL PROTECTED] wrote: On Thu, November 15, 2007 7:00 pm, Ryan Scott wrote: Does anyone know how to fix this? I tried using darwin ports to upgrade but leopard keeps overlaying the install with 2.0.6 which does not work for my application. What were they thinking baking this into the operating system. This is almost as bad as the Java Story. Are they trying to drive developers away from Apple on purpose? What's wrong with putting v2.0.7 ahead of v2.0.6 on the PATH? Leopard is a unix machine, after all. Seriously. That's all I do. Latest maven, etc go in /usr/local/dist. Then links to /usr/local/dist/maven-2.0.7/bin/* go in /usr/local/bin. In my ~/.bashrc: export PATH=/usr/local/bin:$PATH This works perfectly fine, never gets hit by an Apple update. -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Getting Hibernate3's hbm2ddl to generate SQL but not wipe my db?
Hey everyone, I'm trying to get the plugin to generate my SQL code, but I can't seem to do it without it trying to connect to my db. Is there an option that tells it to generate the .sql, but not run it, clobbering my existing db? Thanks, -ls -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
pom.basedir blanked out with Netbeans 6?
Hey all,
I'm having trouble with ${pom.basedir} in my project. I have a few
XML files used by DBUnit, but DBUnit won't find the files when run in
netbeans (runs great on the command line).
The relevant parts:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddbunit-maven-plugin/artifactId
dependencies
dependency
groupIdmysql/groupId
artifactIdmysql-connector-java/artifactId
version5.0.5/version
/dependency
/dependencies
configuration
drivercom.mysql.jdbc.Driver/driver
formatflat/format
urljdbc:mysql://localhost/quickstart/url
username--/username
password--/password
dataTypeWarningtrue/dataTypeWarning
/configuration
executions
execution
idtestdata_upload_vto/id
phasetest-compile/phase
goalsgoaloperation/goal/goals
configuration
typeCLEAN_INSERT/type
src${pom.basedir}/src/test/data/db_vto.xml/src
urljdbc:mysql://localhost/vto/url
/configuration
...
I get this back:
[ERROR]BUILD ERROR
src/test/data/db_vto.xml (No such file or directory)
Any ideas why ${pom.basedir} is apparently blank?
Where do I find documentation on the builtin properties like ${pom.basedir}?
And yeah, the file's still there :-)
Thanks in advance,
-Lally
--
H. Lally Singh
Ph.D. Candidate, Computer Science
Virginia Tech
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why Maven is Hard?
On 9/28/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Lee Meador wrote: That sounds as easy as herding cats. Trying to get all the people on the user list to NOT do anything is unlikely. The fact is, as I see it, its easier to just give a quick answers to questions that strike my fancy than it is to hunt it down in the docs and point them to it. That allows me to limit the time I have available to invest in Maven. If I give the the URL directly, they don't know how to find it in the future. What could be easier to find than a URL? Just add a bookmark/favorite. If I want to tell them which links to click to get there, its a pain for me. Its also likely to change in the future (as it has in the past when the docs were rearranged). FInally, typing in a list of things to click is error prone and easy to get wrong. Maybe someone (or ones) would volunteer to collect the questions from the newsgroup and transfer them to the site if someone else would reply to the interesting questions with some magic words that could be searched on. So, for example, I see what seems to me to be a FAQ with a useful answer in some thread on this list. I reply with the magic word FAQCANDIDATE in the reply. I picked one word because Google searches for two words differently than one word. Then the collectors could search for that word and come up with a short list of user list threads to mine for good FAQ entries. This is exactly what the user wiki can be used for. If people on this list would go the extra bit and add these FAQ candidates (plus answers of course) to the user FAQ we'd have won a lot. Sure, people are actually happy to do it, but it's gotta be straightforward to do so. The wiki 'answered questions' faq has all the good answers in it, and it's not the FAQ list on the side of the maven.apache.org page. It's not even the Wiki page you hit when you go to the wiki and hit the FAQ. Instead we get the unanswered questions, which is not helpful. Earlier today I finished adding the questions answers from the FAQ on maven.apache.org to the Wiki's 'answered questions' faq. So now it can serve as a complete replacement for the maven.apache.org page. Can we get that one linked to on the left-hand sidebar now? -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Improving Maven Site Docs
On 9/28/07, Kevin Jackson [EMAIL PROTECTED] wrote: Hi, Regarding the XML thing (OT wrt documentation - sorry). XML basically sucks as a human readable format, it's a more verbose form of tree/list syntax (like s-expr). One problem I have with mvn that I don't have with Ant is that there are no 'shorthand' options in mvn ie: Agreed. There's no reason we can't have a shorthand translation to make this more readable. I like Spring's ability to add in new tags. The tags can serve for configuration of plugins (the plugins defining the tags), or be shortand. And seriously, a simple Java-based graphical editor wouldn't hurt. It's not fantastic, but Swing does the job. Or a plugin for a popular IDE. -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Improving Maven Site Docs
I just merged in the questions from the main FAQ on the maven site (http://maven.apache.org/general.html) into the 'Answered Questions' portion of the Wiki FAQ (http://docs.codehaus.org/display/MAVENUSER/FAQs-1). The latter is a *lot* bigger, but is also really, really buried. I promised to finish it yesterday, but my new computer came in early :-) Would it be possible to have that left-hand FAQ link to the Wiki FAQ? It'll also let people add in other FAQs Answers a lot quicker. -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: my lobotomy [was: Improving Maven Site Docs]
Actually, the model of 'shortcut translates to raw maven' may really be the crux in getting maven really usable --- syntactic sugar can be really effective. -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why Maven is Hard?
On 9/27/07, Wayne Fay [EMAIL PROTECTED] wrote: On 9/26/07, Tomasz Pik [EMAIL PROTECTED] wrote: Example - please, try to find out how to skip executing of tests during build starting from http://maven.apache.org OK, I'll bite... starting at http://maven.apache.org on the left, click on Wiki scroll down to Children, click on FAQs, see its not there click on previously answered questions (or click back and click on FAQs-1) oh look, there it is -- Testing How do I skip unit tests when building a project? The fact that people can't find it, and are obviously dedicated enough to the project to join the mailing list, proves that the navigation is insufficient. Admittedly, I'm not sure why we have 2 FAQ pages in the Wiki, plus another FAQ on the main Maven site. But I also don't think this is all that horrible. Obviously you can't expect to find every answer this easily but common questions should be. So the next step seems (to me at least) to be determining what are those common questions, as I mentioned in Brian's thread on improving site docs. This is something that users like yourself must participate in if we hope to have any chance of success in this effort. Why not merge them? (Also if you Google for maven skip unit test there's a number of hits right away. I personally feel that answers found via Google are no less valid than others, especially if you add the site:maven.apache.org directive. To say nothing of all the hits in the mail list archive if you search for this.) If you have to use google to search a website, the navigation is broken. -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why Maven is Hard?
On 9/27/07, Antonio Petrelli [EMAIL PROTECTED] wrote: 2007/9/27, Lally Singh [EMAIL PROTECTED]: If you have to use google to search a website, the navigation is broken. Partially true: information should be easily available both through search engines and navigation links (it's Jakob Nielsen opinion, and mine obviously :-) ) Antonio I agree with Neilsen. Of course, the 'easily available .. navigation links' part fails here. Hence the '/have/ to use google'. -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why Maven is Hard?
Ok, enough complaining out of me. If I could change all the files directly, I would. But, here are what I think would really help ASAP. 1. The front-page link to the 'Users Center' should instead point to the Maven Documentation Index http://maven.apache.org/guides/index.html. It's really the starting point for documentation, so put it there. 2. The big FAQ is the 'Answered Questions' in the Wiki. Link to that instead of the existing one (http://maven.apache.org/general.html). -- I just got an account with the wiki. Today I'll copy any FAQs in that page back to the Wiki page, so we don't lose anything. 3. Some general Re-org of that 'Documentation' tab on the left-side navigation. Some of those pages are just links to others, and can be collapsed. Others seem like articles. Ok, screw it, I'm in all the way. How can I contribute new content? I'll start doing a basic manual for Maven. Not that I know much about it, but I'll start squeezing that out of the source, existing docs, mailing list. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why Maven is Hard?
On 9/27/07, Antonio Petrelli [EMAIL PROTECTED] wrote: 2007/9/27, Graham Leggett [EMAIL PROTECTED]: The idea that it's free, what do you expect? quality? undermines confidence in both maven and open source in general, and this doesn't do the maven project any favours at all. Well in fact I think open source software has a higher level of quality when compared to proprietary software. Probably we all have seen proprietary code that is badly documented, written, engineered, etc. For example, I remember the story of Interbase DBMS (I can't find the link, sorry) when it was released as open source: the Firebird team had to fix 25000 compilation warnings! But think bigger: if you try to get docs from Oracle website, you will find almost nothing. If you want docs, you have to go to AskTom or some .edu websites :-( I'd argue that software quality's independent of it's open-ness. For open source, you have the argument that anybody can go in and fix it. Of course, any nontrivial software requires quite an investment to go in fix. For commercial software, you have someone that's got their paycheck depending on people's satisfaction with the software. Of course, you have monopolies where the customer has no choice. It really comes down to how the individual project is managed. Make quality a priority, and the software has high quality. Make it a low priority (e.g. it's free, I'm doing it in my spare time, if you don't like it, don't use it), and you won't have high quality. So, just b/c a project's open doesn't let people off the hook about quality. The open-source fairy won't come in one night and fix all your bugs or write your docs for you. -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Improving Maven Site Docs (was maven is hard)
I put in some suggestions in the original thread 'Maven is Hard'. As for plugin docs, how about modifying the plugin API to support documentation? Embed basic documentation in the plugin directly. Enough so that 'mvn -help' could list the appropriate docs for the plugins listed in the pom? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Improving Maven Site Docs
On 9/27/07, Alan D. Salewski [EMAIL PROTECTED] wrote: I'm not suggesting that the maven 2.x 'install' build life cycle phase be renamed at this point because maven is well-enough established that doing so would be needlessly disruptive. But, thinking back to my pre-maven-lobotomy days, it would have been nice if it did not violate the principle of least surprise on this point. To the extent possible, new approaches and new tools should leverage users' existing experience as much as possible. Some aliases could be useful. Just have an alias called 'available' that maven translates to 'install'. Similarly, a command line option -t which translates to -Dmaven.test.skip=true :-) -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Improving Maven Site Docs (was maven is hard)
On 9/27/07, Wayne Fay [EMAIL PROTECTED] wrote: 1. If maven has no pom in current directory. mvn should display help similar to this from perforce: This sounds reasonable. Other people have requested similar functionality. We should make sure this lands in JIRA for future implementation. 2. have mvn help be able to run out of the box with *no downloads* being required. I agree, but I'm not sure how it should be implemented given that help is simply a plugin like all the others. So we'd need to bundle it with the zip, and then force the user to run a script to install it in the proper place etc as part of the installation. And then if they change their local repo cache location, they'll need to run it again to copy it there too. Have a template repository ship with the maven distro, which maven copies into the appropriate place (e.g. ~/.m2). That way the basis plugins are in place. Also, that'd make it nice for those behind firewalls. They could just take their repo after 'mvn compile' and shove it back into the maven install folder. Rezip that up and give it to your devs so they can use out of the box. 4. if a pom is broken mvn should offer a suggestion about how to fix it. What kind(s) of broken poms should be recoverable/detectable/fixable? Other than XML which is not well-formed, I very infrequently get broken poms personally, so I'd like to hear more suggestions. Does it validate the XML yet? As a start, just print out the results of a good XML validator... -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why Maven is Hard?
On 9/26/07, Wendy Smoak [EMAIL PROTECTED] wrote: (There *is* a doc standard that they have to pass prior to being promoted from the sandbox and released. Does it need to be changed?) YES. Right now the docs tend to look 100% autogenerated and be 0% useful. It's tough to find the useful material in all the autogenerated and unnecessary fluff. Just a description of all the options (e.g. reference documentation) and an example is all I'm asking for. Some boilerplate in there in how to set up plugins (in general) would also be nice. On 9/26/07, Rodrigo Madera [EMAIL PROTECTED] wrote: Make the Better Builds book available directly through the Maven site WITHOUT registration. That'd be nice. Even before hearing back from the respective authors, HOW ABOUT LINKING TO THEM I don't mind registering. I mind finding out about the book randomly from the mailing list or google. -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why Maven is Hard?
The user center. Sorry, didn't mean to be so harsh about it. But when I see 5 tiny links on the user center, I see that there isn't much documentation on the site. I stop looking on the site for anything else -- I hit google. On 9/26/07, Tim Kettler [EMAIL PROTECTED] wrote: Lally Singh schrieb: [...] That'd be nice. Even before hearing back from the respective authors, HOW ABOUT LINKING TO THEM I don't mind registering. I mind finding out about the book randomly from the mailing list or google. Just open the maven website and click on Documentation-External Resources. Is that too hard to find? Where would you place the links? -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why Maven is Hard?
Documentation is 100% the largest weakpoint of maven. On 9/24/07, Steve Mactaggart [EMAIL PROTECTED] wrote: Case in point http://maven.apache.org/guides/mini/guide-multi-module.html Something that is really useful, but still non existant. Another datapoint: I've read both books, been using it daily since January, and still don't feel like I have a handle of how it all works. Whatever tutorial information out there has to explain, at some level, of the steps data maven uses to do what it does. In ant, it's simple: the tags describe the procedures used. In maven, so much of it is implicit (but un/under documented) that it's tough to see what's going on. A description of maven's internal procedures is needed -- to turn that black box white. There's no fundamental reason why maven can't be well documented. _Just tell us how the thing works_. From that, you can describe how other things hook onto maven, and thusly how it and the plugins work. It's also a great way to entice developers to contribute, if they already have a working idea of how the system works internally. Also, some basic listing functionality of what maven takes in would be nice. Even if it's web based. I've found mvnrepository.org to be great, but that's something I found via googling. But how about something for archetypes? I've found something now and then through extensive googling, but this really should be on the 1st page of documentation for maven. As should a search box for mvnrepository. That's probably the best first test to use for the quality of maven's docs: how much can you figure out and use without having to hit google? Just using maven.apache.org, how functional is a new developer? Mailing lists are another thing I'd blacklist from this test. If someone has to ask about something on the mailing list, the documentation has failed. And while plugins having entire sites is nice, it'd be great if we could generate a reference manual (even if it's another HTML website) that covers every plugin that we're using in a project. If it's there, I haven't found it. This isn't to discourage the existing documentation efforts -- but prioritize documentation to be #1. I think for most users, maven's good enough by far, and a lot better than the competition. The advantages it gives are well worth it, _if_ they could figure out how to use it. -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Eclipse, Hibernate Tools
On 2/26/07, John J. Franey [EMAIL PROTECTED] wrote: Lally Singh wrote: how do I get maven to do whatever needs to be done to process my hibernate annotations? If you are using java 5 annotations and maven 2: Nothing, aside from compiling with java 5 or better, homing hibernate and java persistence configuration files into src/main/resources directory, and obtaining the hibernate artifacts into your repository. This answer does not apply to javadoc annotations (i.e., source code generation via xdoclet) or maven 1. Annotations are a java language construct and are 'processed' by java compilation. The java compiler puts annotation data into the output class files for the hibernate libraries to read. Wonderful, thank you. However, nothing's getting generated into src/main/resources (that's just got the original cocoon spring stuff in it). Is there another maven target I should run? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse, Hibernate Tools
Hey all, maybe not the right place to ask, but I didn't know who else. I've got a Maven project set up in eclipse with the eclipse-maven plugin. I've annotated some classes for Hibernate. I'm not really too familiar yet with Java's annotation system, so I'm at a loss for how to get the annotations 'processed' (do they need processing?). Specifically, how do I get maven to do whatever needs to be done to process my hibernate annotations? Latest version of hibernate tools as of last week. Thanks for any help, -ls - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
