Yes, to compile 1.5 classes, you must use a 1.5 (or greater) JRE. But
you also must set the 1.5 configuration, otherwise it defaults to 1.4
classes with the 1.5 JRE.
Wayne
On 11/11/06, jiangshachina [EMAIL PROTECTED] wrote:
Hello,
configuration
source1.5/source
target1.5/target
Hi,
otherwise it defaults to 1.4 classes with the 1.5 JRE.
I'm using JDK1.5.0_08, but Maven uses 1.3, but 1.4, as default.
a cup of Java, cheers!
Sha Jiang
Wayne Fay wrote:
Yes, to compile 1.5 classes, you must use a 1.5 (or greater) JRE. But
you also must set the 1.5 configuration,
I already posted the same question a few days ago, but no answer yet. Maybe
we should file a bug on this? It is annoying when converting to Maven 2,you
don't get the same functionality.
regards,
Wim
2006/11/11, Olivier Catteau [EMAIL PROTECTED]:
Hi,
I have a lot of unit tests in my app.
I hope someone can spare me some time to clear up my investigations.
I am porting from maven 1 to maven 2, and we had begun using junit 4.1
by using the JUnit4TestAdapter like so:
/**
* Wrap the new junit4 testcase in a 3.x style suite
* to be recognized by eclipse runner and maven
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks!
I have the following problem with a Maven 2 project:
My project is in a CVS repository and the target-dir is excluded from
CVS via .cvsignore. As long as I build with Maven everything is fine.
When I generate a Eclipse project out of
On 11/9/06, jiangshachina [EMAIL PROTECTED] wrote:
I may have known the goal of src/main/assembly(assembly descriptor files
used by maven-assembly-plugin).
Now I want to ask what files should be put at src/main/conf?
It seems that the folder would include configuration files, but which
Got 'em.
Thanks for the heads up!!
Ed
On 11/11/06, jiangshachina [EMAIL PROTECTED] wrote:
Hi Ed,
I tried the download site just now
http://www.mergere.com/m2book_code.jsp
but all is OK.
You can try again. Good luck!
a cup of Java, cheers!
Sha Jiang
Ed Young wrote:
The links have been
Hmmm, thank you for looking, I'll take another look.
Regards, Kelvin.
On 10/11/06, Vincent Siveton [EMAIL PROTECTED] wrote:
Hi Kelvin,
I did mvn javadoc:javadoc (with 2.1) on tuscany trunk:
https://svn.apache.org/repos/asf/incubator/tuscany/java
No error here. Are you sure that commonj is
Hi *,
Trying to prepare an upload bundle...
C:\project\qalab\maven2-qalab-pluginmvn repository:create-bundle
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'repository'.
[INFO]
[ERROR]
On 11/12/06, Benoitx [EMAIL PROTECTED] wrote:
C:\project\qalab\maven2-qalab-pluginmvn repository:create-bundle
It's repository:bundle-create (not create-bundle) and you shouldn't
need to add it to your pom.
mvn repository:create-bundle
...
The plugin
Thanks Wendy, I saw both and had the feeling that I had tried both...
obviously not.
Thanks for your reply
Benoit
Wendy Smoak-3 wrote:
On 11/12/06, Benoitx [EMAIL PROTECTED] wrote:
C:\project\qalab\maven2-qalab-pluginmvn repository:create-bundle
It's repository:bundle-create (not
I am running :
mvn 2.0.4
JDK 1.5
subversion
Multiple project structure!
*Why does this build has a SUCCESSFUL status? It did not do an update?*
*Is there something wrong with my pom.xml? This did work back in July 2006!*
**
**
Parent pom.xml
|
| Child pom.xml
If am trying to do a
Thanks for pointing out the issue with the basicClientJar. I fixed the code
this morning along with the forceGeneration and lineNumbers flags. I pushed
a new snapshot up to the codehaus repository as well. Let me know if you
have any other issues.
Scott Ryan
Chief Technology Officer
Soaring
On Sun, Nov 12, 2006 at 11:08:21PM +1100, J. Matthew Pryor spake thus:
*snip*
I am porting from maven 1 to maven 2, and we had begun using junit 4.1
by using the JUnit4TestAdapter like so:
*snip*
This worked fine for maven 1 and since I didn't know any better, was
ported over to maven 2,
Hi
From http://maven.apache.org/plugins/index.html there is no link to the
Repository Plugin, however, there is a page:
http://maven.apache.org/plugins/maven-repository-plugin/index.html
But the FAQ and usage pages are missing... What is happening with this
plugin?
Is there a replacement? Is
On 11/12/06, Benoitx [EMAIL PROTECTED] wrote:
From http://maven.apache.org/plugins/index.html there is no link to the
Repository Plugin, however, there is a page:
http://maven.apache.org/plugins/maven-repository-plugin/index.html
But the FAQ and usage pages are missing... What is happening
Yes, you naturally need to use a compiler at least as high as the code you
wish to compile in. If your Maven is running on JDK 1.4, and you wish to
compile code as 1.5, you will need a 1.5 compiler. You can point to a
1.5compiler in the following way:
I don't know why your build failed, but this table of file/dir statii
from the Subversion Book may help you figure it out:
http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.tour.cycle.examine.status
Maybe the svn repo specified on the maven command line does not match
the repo (in a
Hello Wendy,
I haven't seen it used, and I don't think Maven does anything with it
by default right now.
Oh, that's means that the directories just are recommended by Maven, but
Maven does nothing for it as default.
Then I have to deal with the directories by manual.
What's a better way to
On 11/12/06, jiangshachina [EMAIL PROTECTED] wrote:
Oh, that's means that the directories just are recommended by Maven, but
Maven does nothing for it as default.
It probably means that during the design discussions, someone thought
a 'conf' directory would be useful. I haven't seen it
I'm running Archiva from a svn checkout, with the Jetty plugin. (mvn jetty:run)
I've created the admin user and a managed repo, and given the 'admin'
user the repository observer role for that repo.
From the Administration page, if I click on the WebDAV URL:
Does the directory you configured already exist? I don't think
Archiva creates it at present.
This isn't anything to do with Jetty - we use the could.it webdav
library (as you can see through the trace, it comes from a
RepositoryAccess servlet in our code).
- Brett
On 13/11/2006, at
I don't think this is available as a Maven Mojo yet. But it would really
cool to have.
I hit similar situation at work where I needed to revert a release. The
other alternate is to delete the release tag (referring to CVS, but not
sure about other SCMs).
Any one else has any ideas? May be
The problem is that the build passes, because the src code is not being
updated.
So, I ran the command from manually, and I narrowed it down to this command.
Thanks,
On 11/12/06, Max Cooper [EMAIL PROTECTED] wrote:
I don't know why your build failed, but this table of file/dir statii
from
Hi Wendy,
If you want a file to be in the archive, then put it under
src/main/resources (or src/main/webapp, as the case may be.)
The two approaches I have used.
I just want to know whether there are other ways.
But the two approaches above are most direct and easy :D
a cup of Java, cheers!
Thanks for the replies guys. Even i first thought of having a seperate
project for servicegen and appc, but didn't build on the thought. Looks like
i should try it out. As of now i've appc defined in an execution and in the
package phase.
I hope the servicegen mojo in the plugin will solve a
Hi Olivier and Wim,
Try using the --quiet option. It will change the logging level to ERROR.
Hope this helps.
Dawn
Wim Deblauwe wrote:
I already posted the same question a few days ago, but no answer yet.
Maybe
we should file a bug on this? It is annoying when converting to Maven
Hi Olivier,
In your parent POM, use:
dependencyManagement
dependencies
dependency
groupIdcom.mycompany.app/groupId
artifactIdmy-subapp/artifactId
version${project.version}/version
/dependency
/dependencies
/dependencyManagement
${project.version}
Hi,
Is there a way to have a report that shows the changes between the
sources of two releases?
Thanks!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Ok then,
in the maven eclipse plugin i found the following that could be of use?
parameter
nameadditionalConfig/name
typeorg.apache.maven.plugin.eclipse.EclipseConfigFile/type
requiredfalse/required
editabletrue/editable
descriptionAllow to configure
30 matches
Mail list logo