That solved the problem, thanks.
For those interested, I simply added this to the pom :
profiles
profile
idjettyConfig/id
dependencies
dependency
groupIdjavax.servlet/groupId
artifactIdjsp-api/artifactId
Thanks Ian for the answer. Yes, I was refering to developer connection
element.
I have one other question.
I would like to tag before a build, then pull the tag, and build it.
We want to the tag with project name plus timestamp for daily/test
builds so is it possible to specify this new tag in
I find that we can share any number of artifcats withing mulitple projects
thru the repository.
i mean we can take repository as a common place,...
For example,
If the built artifact of project A is to be needed for another project
B,..we can place the built artifact of A in the repository so
On Sat, 1 Apr 2006, raja bangaru wrote:
You can't. Repositories are a core maven concept; it is the only way to
share artifacts.
Why don't you want to put A in a repository?
(mvn install - local repository, no problem, right? it's just a
'temporary' directory anyway).
-- Kenney
I find that
When you upload the files using deploy-file, it is creating the files with
following persmission. -rw-rw. If I change permission to -rw-rw-r--
(664) it is able to download the file.
Thanks
Gautham Pamu
On 3/7/06, Carlos Sanchez [EMAIL PROTECTED] wrote:
Please create an issue at
When you upload the files using deploy-file, it is creating the files with
following persmission. -rw-rw. If I change permission to -rw-rw-r--
(664) it is able to download the file.
--
-Gautham Pamu
Roger,
There is a sar plugin, and some time ago I submitted a wsr plugin as
well if you are using JBoss web service archives. Additional I
updated the ear plugin some time ago to recognize both wsr files. I
am not sure what was committed, as I've been running off my own
builds of these
I'm trying to convince the m2 site plugin to build a site from an
m1-formatted project. (Using 2.0.4-SNAPSHOT from the vote thread.)
I've created src/site/site.xml (pasted the example from the guide),
and configured as follows:
plugin
See http://jira.codehaus.org/browse/MECLIPSE-37
Mark
On 01/04/06, gdub [EMAIL PROTECTED] wrote:
Hi-
I'm wondering if this is a bug or just
intended new behavior. I also don't
know if it is a plug-in issue or a
Maven application issue.
Recently, I installed 2.02 on my laptop
(I use 2.01
Use scopesystem/scope everywhere.
Good luck managing it.
Wayne
On 4/1/06, Kenney Westerhof [EMAIL PROTECTED] wrote:
On Sat, 1 Apr 2006, raja bangaru wrote:
You can't. Repositories are a core maven concept; it is the only way to
share artifacts.
Why don't you want to put A in a repository?
Cool, I honestly wasn't aware that you could include dependencies in
the profiles like that, I'm obviously pretty new to profiles. ;-)
I'm curious if you could combine dependencyManagement to handle
version numbers in pom.xml along with these profiles to include
certain deps with scope=compile in
[sending back to users list]
On 01/04/06, gdub [EMAIL PROTECTED] wrote:
I see. Thank you Mark. So, bottom line, I'm
SOL for now. I hope a solution is implemented
soon. This problem precludes me from upgrading
Maven on my primary workstation.
Yep, I think this situation hinders more people
I've re-read the MECLIPSE-37 discussion
and thought a bit about the bigger picture:
Maybe the root of the problem is that
plug-ins like eclipse are logically outside
Maven's scope.
Arguably, Maven as a project lifecycle
management tool should not be concerned with
how developers view and modify
mvn -U i believe should force a check for updates. but depending on
how your repositories are configured, you might not get all available
updates (ie snapshots) esp if Central/ibiblio for some reason does not
have the most recent version of a particular dependency ie its out of
sync with another
Hi,
Is there a way to force Maven 2 to put jar files in a specific order on the
classpath? I noticed that the jar files as defined in the dependencies section
are not added to the path in that order.
Is the order arbitrary? Is there something that determines the order?
I have some problems
You need to build the skins with:
mvn -DupdateReleaseInfo=true install
until they are released.
You shouldn't need that configuration in the plugin for xdocs, as that
directory is the default.
- Brett
On 4/2/06, Wendy Smoak [EMAIL PROTECTED] wrote:
I'm trying to convince the m2 site plugin
On 4/1/06, Brett Porter [EMAIL PROTECTED] wrote:
You need to build the skins with:
mvn -DupdateReleaseInfo=true install
until they are released.
Thanks.
You shouldn't need that configuration in the plugin for xdocs, as that
directory is the default.
One of the trial by error attempts. :)
It's reasonable to expect, but it doesn't handle that currently.
Please put it in JIRA, I'll make sure it happens by 2.0.
- Brett
On 4/2/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 4/1/06, Brett Porter [EMAIL PROTECTED] wrote:
You need to build the skins with:
mvn -DupdateReleaseInfo=true
On 4/1/06, Brett Porter [EMAIL PROTECTED] wrote:
It's reasonable to expect, but it doesn't handle that currently.
Please put it in JIRA, I'll make sure it happens by 2.0.
Done: http://jira.codehaus.org/browse/MSITE-109
Thanks,
--
Wendy
I do believe that it will be part of the next release of the site plugin.
-Stephen
On 3/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Wayne,
Thanks for your reply. I agree is not painful in anyway, my
point is, its something that could easily be managed by Maven as many
other
20 matches
Mail list logo
