Hi,
I am also trying to generate a fortify report of a java source code using
maven. But i am not able to do it. Can you please revert me back of how you
did it??
--
View this message in context:
http://maven.40175.n5.nabble.com/Fortify-and-Maven-tp118623p5709785.html
Sent from the Maven -
What problems do you run into? Have you got access to the maven site
docs for the plugin? If not, get hold of that from the Fortify
support.
/Anders
On Fri, May 25, 2012 at 11:22 AM, Swagatika
swagatikamahapatr...@gmail.com wrote:
Hi,
I am also trying to generate a fortify report of a java
Hi,
Actually can you please guide me with, where can I get any steps to
generate a fortify report using Maven.
Is there any plug-inn that we can use to generate the fortify report
?? I downloaded and installed the fortify360 plugin and the
maven-fortify plug-in and then added the dependencies
Did you get hold of the Maven site docs for the Fortify plugin?
You shouldn't declare a dependency to the plugin, but add plugin
bindings. I don't recall the exact steps, but they are described in
the Maven site for the plugin and/or the Fortify documentation.
I believe you should be able to get
Can you please tell me the exact location for the Fortify
documentation. I searched a lot but i am not able to get any info.
On 5/25/12, Anders Hammar [via Maven]
ml-node+s40175n5709794...@n5.nabble.com wrote:
Did you get hold of the Maven site docs for the Fortify plugin?
You shouldn't
Did you read my mail where I said that you can get it from the Fortify support?
Please, this is a mailing list for generic Maven questions. The
Fortify product comes with professional support, please use it!
/Anders
On Fri, May 25, 2012 at 12:42 PM, Swagatika
swagatikamahapatr...@gmail.com
I have a project presentation with the following structure:
presentation
src
main
test
In the target directory I am getting:
presentation-1.0.ear
presentation-1.0-tests.jar
What I would like to be able to do is to have test classes to be packages
inside the ear.
I was hoping
I got the error below when try to run mvn install pdf:pdf:
[ERROR] No plugin found for prefix 'pdf' in the current project and in the
plugin groups [com.nbfg.fw.maven.plugins, org
.apache.maven.plugins, org.codehaus.mojo] available from the repositories
[local
The org.apache.maven.plugins:maven-pdf-plugin:1.1 already exists in
the Central repository, so Maven should normally be able to use it. I
would suspect that the Central Repo is not part of the Nexus repo
group 'mdm-public'. You should talk to your Nexus admin about this.
/Anders
On Fri, May 25,
Is it possible to change the name of the folder into which the dependency is
unpacked? Seems like there is no equivalent to the non-unpacked
outputFileNameMapping?
Hi,
Is there anyone using the shade plugin? are you facing this issue?
On May 22, 2012, at 11:06 AM, Saurabh Ajmera wrote:
Hi,
I am using the maven shade plugin to produce a jar which includes contents of
one dependency artifact plus the contents of my current maven module, such
that
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.3.1
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps:
prepare and perform.
Yes, we are using our own internal Nexus repository, not Maven central. I
have the Nexus admin right and I did uploaded the pdf plugin already.
Jirong
--
View this message in context:
On Fri, May 25, 2012 10:09 am, hujirong wrote:
Yes, we are using our own internal Nexus repository, not Maven central. I
have the Nexus admin right and I did uploaded the pdf plugin already.
Jirong
You should NOT be uploading artifacts that are available in external
repositories. Just proxy
In such case the best approach is to create an issue with a sample project
to reproduce the trouble .
And the best of the best attaching a patch which fix the issue :-)
--
Olivier
Le 25 mai 2012 17:40, Saurabh Ajmera sajm...@usc.edu a écrit :
Hi,
Is there anyone using the shade plugin? are
Everything I read is that the RPM will deploy to the repo, but only the WAR
is getting deployed. What do I need to do to get the RPM as well?
Thanks!!
--
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox http://db.tt/9O6LfBX !!
My question wasn't all that clear.
My problem is this. I have a zip dependency that I'm unpacking into my
assembly. I'd like to trim out the root folder of that zip's contents, so I
can just dump the contents of that root folder into my output directory. I'm
having trouble figuring anyway
Hi Oliver,
Thanks for your response. I have created the following jira:
http://jira.codehaus.org/browse/MSHADE-120
Also, I have attached a sample project to help reproduce the issue.
Thank you,
Saurabh Ajmera
On May 25, 2012, at 11:07 AM, Olivier Lamy wrote:
In such case the best approach is
So your problem is with the unzip stage where it is creating a top level
directory and putting the files in it instead of exporting just the
files into the output directory?
Perhaps you want to share your current method of doing that?
Ron
On 25/05/2012 2:51 PM, chad.da...@emc.com wrote:
My
First, our internal network is very slow, so everything we need is stored in
our own internal Nexus. My question is what's the issue with my upload?
Second, follow your suggestion, how can I setup a proxy tells Maven to
retrieve everything from Maven central which is not in our internal
On Fri, May 25, 2012 12:12 pm, hujirong wrote:
First, our internal network is very slow, so everything we need is stored
in
our own internal Nexus. My question is what's the issue with my upload?
Second, follow your suggestion, how can I setup a proxy tells Maven to
retrieve everything from
You should have your repository manager (be it Nexus or some other
brand) proxy the central repo. I would guess that a default setup
includes this already. I know that the Nexus ones does this. Then you
configure your settings.xml according to the one specified in the free
Nexus book:
So your problem is with the unzip stage where it is creating a top level
directory and putting the files in it instead of exporting just the files
into the
output directory?
Perhaps you want to share your current method of doing that?
Hey Ron. It's not that it's creating a top level
Depending on what os you're on, you might have hit MRPM-107. I would
love any input on how to solve this.
/Anders
On Fri, May 25, 2012 at 8:28 PM, Jeff predato...@gmail.com wrote:
Everything I read is that the RPM will deploy to the repo, but only the WAR
is getting deployed. What do I need
This is my first RPM ever AND first time using the rpm-maven-plugin so it
could very well be something I'm doing. I don't think MRPM-107 is my issue
since the RPM is getting built. It just doesn't upload to our internal
Maven repository during the deploy phase.
Here is the log section that
What I would like to be able to do is to have test classes to be packages
inside the ear.
I was hoping that by specifying 'earSourceDirectory' it will put the test
files inside the ear, but it's not happening. Below is my pom.xml. Tnx!
Generally, ears do not contain source code themselves,
Hi, i have added the code in my pom.xml to update from svn every time i
take a build (using scm and build-number plugins) so when i run mvn install
, it does so ..However is there any way to disable this update without
removing the entry in pom ?
If you don't want to perform some part of
(I've never used this plugin, but you piqued my curiosity, so I took a quick
look at it.)
Looks to me like you're running the rpm goal which just generates the rpm,
correct? Have you tried running the attached-rpm goal?
I didn't glean anything from the docs about deploying by default, unless
Hello,
We currently have about 40 different multi-module projects. To date, we have
determined an appropriate release order for the projects by manually parsing
the POM files and making note of the dependencies. We keep our list in a
spreadsheet, and it is re-evaluated with every release
Can't you just look at the reactor order? That will tell you which projects
you would have to release first.
-Original Message-
From: Pimentel, Robert [mailto:robert.pimen...@tgslc.org]
Sent: Friday, May 25, 2012 4:47 PM
To: 'users@maven.apache.org'
Subject: Plugin to determine
Hi there.
We've been doing without multimodules for some time now, so we ended up
with a number of standalone Maven modules and faced a very similar
problem as you do now. We thus created a prototype of a Maven plugin
which extracts the project interdependencies from the POMs which are
deployed
THANKS!!! That was it.
I misunderstood the docs regarding when I should use the 'rpm' vs.
'attached-rpm' goal.
On Fri, May 25, 2012 at 2:30 PM, Matt Walsh
mwa...@chartwelltechnology.comwrote:
(I've never used this plugin, but you piqued my curiosity, so I took a
quick look at it.)
Looks
Any thoughts on this?
On Thu, May 24, 2012 at 10:16 AM, Jeff predato...@gmail.com wrote:
Is it possible to export the build number or the URL of the artifact
(SNAPSHOT and release depending on build) that was uploaded to our internal
repository or any other information about the build and/or
imagine this is both tedious and time-consuming. Do you know of a plugin, or
any (preferably free) third-party tools that can parse a collection of
project POMs and produce an appropriate release order? Additionally, it
I don't know if this would be too helpful for you, but maybe check out
the
34 matches
Mail list logo
