hallo
the trick is to reference the checkstyle config as a dependency and not
directly as a file.
there are some hints at:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
we created a module containing only the checkstyle config. the parent
pom then
hallo
well i hope its that simple :)
just add it as a dependency!
dependency
groupId${project.groupId}/groupId
artifactIdcommon/artifactId
version${project.version}/version
/dependency
this could be a module in the multimodule build too. no difference to
'external'
errors occur.
is there a way to configure the compile plugin to behave correctly?
the release:prepare executes both compiler:compile and
compiler:testCompile but it seems as the first step is 'forgotten' when
it comes to the test classes.
any hints or ideas would be great!
regards
ossi
ossi petz
Hallo
the deploy plugin gives some examples how to pass arguments to the scp
command (sshArgs in configuration):
http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ssh-external.html
settings
...
servers
server
idssh-repository/id
usernameyour username in the
hallo
i encounter a very strange situation with the maven release plugin. we
have done quite some releases but for some reason a release:perform
fails to compile test classes depending on another module.
the setup looks like this:
pom.xml (parent pom)
- module1
- module2 (with test2.jar)
-
Hallo
i have a very weird problem when reating the javadocs using javadoc
plugin version 2.3. this is my configuration in reporting/plugins:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
tags
tag
hallo
i had the sam issue. i switched to an external mysql database:
http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+MySQL
archiva and continuum can share the same users database! that is also my
configuration. actually someone told me this is recommended :)
regards
ossi
Mick
Hallo
i currently try to understand how the assembly plugin works. i have a
multi-module build (lets say m1 to m5) which creates sources and
javadocs when a release is done.
from this point i want to create different zip files
- one which contains the jars of m1, m2, m3
- one which
Hallo
i have a very similar issue (etch mysql 5.0.32):
2007-12-04 17:09:50,777 [main] ERROR JPOX.RDBMS - Error thrown
executing CREATE TABLE `SECURITY_OPERATIONS`
(
`NAME` VARCHAR(256) BINARY NOT NULL,
`DESCRIPTION` VARCHAR(256) BINARY NULL,
`PERMANENT` BIT NOT NULL,
cool!
i needed to change the mysql database charset to latin1 (see other
discussion on mysql 5.0)
thanks!
regards
ossi
Brett Porter schrieb:
yes, and yes. in fact, I would recommend sharing the user database connection.
On 04/12/2007, ossi petz [EMAIL PROTECTED] wrote:
Hallo
thanks
Hallo
I tried to install both archiva and continuum on the same tomcat 5.5.25
/ Java 1.5
When i only install continuum things work fine. When i only install
archiva things work too.
When i install both continuum and archiva i end up with apache derby
exceptions. archiva starts (i guess
, please let me know. :)
Ingo
ossi petz schrieb:
Hallo
I tried to install both archiva and continuum on the same tomcat 5.5.25
/ Java 1.5
When i only install continuum things work fine. When i only install
archiva things work too.
When i install both continuum and archiva i end up with apache
hallo
hopefully this does not end up in thread-stealing...
i'd like to provide some ldap feedback on beta-3 too.
i've managed to configred authentication against our active directory.
users can login to continuum. thats already something!
so lets switch quickly to the problems part :)
a hint? i ll try to figure out the difference.
regards
ossi
Wayne Fay schrieb:
They are excluded by default. You must be doing something special.
Send the relevant portion of your pom and perhaps someone will have
specific advice.
Wayne
On 10/4/07, ossi petz [EMAIL PROTECTED] wrote:
hallo
i
.
well. it seems to happen for a reaseon. so thanks for listening :)
Wayne Fay schrieb:
They are excluded by default. You must be doing something special.
Send the relevant portion of your pom and perhaps someone will have
specific advice.
Wayne
On 10/4/07, ossi petz [EMAIL PROTECTED
hallo
i dont know exaclty when this started to happen:
i added the maven source plugin to the build section.
i noticed the created sources.jar contains the '.svn' folders from the
source directory.
is there a way to exclude them?
thanks a lot :)
ossi
hallo
i dont know archiva. we use shell commands to add 3rd party libs and
sources:
mvn deploy:deploy-file -DgroupId=com.company
-DartifactId=company-common -Dversion=2.0.3 -Dfile=src-common-2.0.3.zip
-DrepositoryId=company-internal -DrepositoryLayout=default
-Dpackaging=java-source
hallo
this might be a stupid question but i never got in touch with apache
derby databases before.
i tried followed the upgrade instructions at
http://maven.apache.org/continuum/guides/mini/guide-data-management.html
the commands i issued:
$ java -Xmx512m -jar
hallo
outofmemory yes, but with reports.
set an env varaiable:
MAVEN_OPTS=-Xms128m -Xmx512m
to allow maven to use more memory. that should do the trick
regards
ossi
Larry Suto schrieb:
Hi I am trying to upload an artifact to Maven repository with
deploy:deploy-file. I am getting a
don't understand why the 'local' profile is not deactivated.
If not possible, should there be another way to meet my needs?
Thanks,
Philippe
On 9/6/07, ossi petz [EMAIL PROTECTED] wrote:
hallo
the profiles are not inherited to child modules, but the effects are. so
the child will not show
hallo
sorry for the confusion. repos defined in a pom dont need a profile. i
have put them into settings.xml, there i got my example from.
when you create different flavours of artifacts (test, stage, prod) the
best practice is to use profiles.
most likely it is only the project that needs
hallo
within the exlipse workspace there is a .metadata folder, there should
be some .log file with the complete stacktrace.
i think isues should go to http://code.google.com/p/q4e/issues/list
regards
ossi
Joshua ChaitinPollak schrieb:
Using q4eclipse, I get a null pointer exception
indeed some wtp support statements would be interesting.
wtp with filtering too :)
ossi
Arnaud HERITIER schrieb:
I tested it a little bit and effectively it's working fine.
Great job guys !!
Is there someone who tested if with WTP ?
Arnaud
hallo
if you have plans to use wtp and m2eclipse you will need to move to
eclipse 3.3 anyway. so plan some upgrades in the near future :)
regards
ossi
Bernard Lupin schrieb:
Hi Carlos,
It seems that Q is only available with Eclipse 3.3. Unfortunately, all our
workstations are currently
hallo
the profiles are not inherited to child modules, but the effects are. so
the child will not show the profile as active but it will work nontheless.
see: http://www.nabble.com/Profile-inheritance-tf2953156s177.html#a8259757
for a better explanation
regards
ossi
Philippe Le Marchand
hallo
yes the order of the repositories is kept when looking for artifacts.
you can define repositores in settings.xml or in a profile in a parent pom.
but from here: do you plan to put different artifacts with the same
groupId/artifactId/version into your repositories?
so dev-repo will
Hallo
indeed initial project creation is a bit a mess. to stick with the maven
standards i used src_main_java as initial source folder. then you need
to go through the eclipse files (.classpath, .project, .settings/*) and
modify the paths accordingly (search / replace).
This should allow to keep
Hallo
another weird problem :)
i have two repositories defined, one for snapshots, one for releases.
when i add a dependency like:
dependency
groupIdgroup.id/groupId
artifactIdartifact-id/artifactId
version[2007.2.,2007.3)/version
you mention:
http://jira.codehaus.org/browse/MNG-2994
Cheers,
Mark
On 16/07/07, ossi petz [EMAIL PROTECTED] wrote:
Hallo
another weird problem :)
i have two repositories defined, one for snapshots, one for releases.
when i add a dependency like:
dependency
Hallo
both seems equally possible. you can inherit your pom from a prent pom
without defining modules in the parent.
you would need to release the parent on its own prior to its 'children'.
if you frequently release versions for every client a parent pom with
configured modules has some
hallo
have you configured the modules in your parent pom? (modules section)
if so the generation of the site at the parent pom location should do
the job
regards
op
Sylvain Mazaleyrat schrieb:
It's work fine when you have just one module.
When I do :
$ mvn site
$ mvn site:deploy
I
:)
the first link is easyier to find (maven page, plugins by category,
checkstyle). the second was from google.
Dennis Lundberg schrieb:
ossi petz wrote:
did i post that link? :)
those instructions will create a cyclic reference for the mentioned
'build-tools' project. better do
Hallo
I am experimenting with version ranges. I read along chapter 3.6 and
some pages:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
http://docs.codehaus.org/display/MAVEN/Extending+Maven+2.0+Dependencies
but things dont seem to work is i would expect
hallo
how did you import the project?
are you using the eclipse:eclipse goal to create the .project file?
or are you using the m2eclipse plugin? if so is it enabled for the project?
i assume those libraries where downloaded from you own repository? what
does your pom say for the jars
Hallo
are you using webdav to deploy the file into the repository? if so has
there been another deployment of that file from another location?
409 indicates versioning issues in webdav. but may not be related to
webdav at all.
i would try using file:// instead of the url or using the
hallo
well parent poms and relative paths. a long story.
have you issued the site command from the sub-modules?
but the release is done from the parent pom?
it seems the checkstyle plugin is not aware of that difference and is
looking at the wrong location.
i do both site and release from
well after reading along in the docs:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
kinda solves this issue :)
(havent tested it yet but it looks good)
Jon Strayer schrieb:
On 7/10/07, ossi petz [EMAIL PROTECTED] wrote:
hallo
well parent poms
did i post that link? :)
those instructions will create a cyclic reference for the mentioned
'build-tools' project. better do it this way:
http://maven.apache.org/plugins/maven-checkstyle-plugin/tips.html
works :)
ossi petz schrieb:
well after reading along in the docs:
http
hallo
well that should not matter. the checkstyle plugin dependency is
resolved by its groupId/artifactId. as long as that jar is 'somewhere'
it should be possible to include it as normal dependency without
creating modules.
so the plugin section for the checkstyle plugin gets a
Jens Hohl schrieb:
i have an Multi project with lots of artefacts. What's the best solution
deploying all Artefacts ?
what do you need to deploy (standalone apps, webapps, ...?) and where do
you want it do deploy? and are there variants of the same deployment?
best way is using maven to do
Hallo
thanks for the input!
so if i use relative paths for the parent pom the maven release plugin
will fail?
so you need to create a subversion repository for every parent-pom?
i tried to 'steal' some ideas from the apache subversion repository. but
that pom structure is beyond what i can
Hallo
from what i've read in this list somewhere:
profiles are not inherited to sub-modules. so the profile will not
appear as activated. but nontheless the effects of a parent-pom profile
are inherited to the child-modules.
so es you should be able to define a profile in the parent pom and
hallo
this might be obvious for everyone. but well - i could not find clear
recommendations on how to do this the best way.
i have a multi-module build:
parent pom.xml
- module-1
- module-2
- module-3
the modules are stored in a subversion repository:
http://repos/trunk/module-1
hallo's
i just noticed that the emf common dependency
http://repo1.maven.org/maven2/org/eclipse/emf/common/2.1.0/
uses 'common' as artifact id. this is kinda scray, as 'common' is a too
widely used name.
when i execute:
mvn dependency:copy-dependencies
all 'common' dependencies with the
hallo
did you try to issue the scp command with another client? (manually on
the command line).
does the 'permission denied' relate to the scp command login or to
filesystem permissions?
these is my config from pom.xml:
...
distributionManagement
repository
idreleases/id
/07, ossi petz [EMAIL PROTECTED] wrote:
i know how to add a non-free (commercial) jar into a local repository. i
use deploy:deploy-file to achieve this:
...
how can i add the sources to this jar file? (packed in core-2.0.0.zip)
is there some other packaging type? (i havent found the available
hallo
this is probably some stupid question.
i know how to add a non-free (commercial) jar into a local repository. i
use deploy:deploy-file to achieve this:
mvn deploy:deploy-file \
-DgroupId=com.somesoft \
-DartifactId=core \
-Dversion=2.0.0 \
-Dfile=somesoft-core-2.0.0.jar
hallooo
well it may does not help at all but welll... :)
the 'better builds with maven' book contains a chapter where the spring
framework is migrated to maven2. in this example it is shown how to
treat special classes that are 1.5 dependant. i didnt paid that much
attention - but it is
Hallo
from what i understand maven identifies its dependencies by groupId and
artifactId, the version itself seems to relevant to retrieval of the jar
file only.
maybe you could manually add that dependency into the pom.xml?
Marouane Amraoui schrieb:
Hi.
the fileX-1.0.jar
As soon as the bad gateway (502) turns into a good one i will have a
look at it :)
this year the apachecon website seems to be more down than alive...
Brett Porter schrieb:
For those that are interested in attending ApacheCon, it's on in
Amsterdam, 1-4 May. Details are available at
hallo
what is the command line and path you used to fire up maven?
and where did you put these profiles?
Christian Goetze schrieb:
Why does this not work?
profile
idproxy/id
activation
property
nameenv.MAVEN_PROXY_URL/name
/property
/activation
Hallooo!
Thanks for your input. This did solve my issue!
kind ragards
op
Nick Stolwijk schrieb:
I guess that at one time during release:prepare the clean phase is
executed, which causes the target directory to be deleted. (Including
your working copy information i.e. .svn directory) In my
hallooo
i am trying to get me thorugh the release steps using maven 2.0.5 and
subversion.
i have created several modules (pretty similar to the spring migration
example from the book) abd done a checkout.
within the directory of the parent pom i execute:
# mvn release:prepare
this fails
53 matches
Mail list logo
