easiest way to create debian packages using jdeb/assembly?

2015-04-12 Thread Kevin Burton
I’m currently using jdeb to create debian packages.

I use the assembly plugin to create a dependency set of .jars, then I use
jdeb to package everything together.

The problem is that it’s a HUGE chunk of boilerplate that I have to keep
copying.  We have about 10 daemons right now in a micro services
environment so it’s becoming onerous.

I tried to create a parent pom to inherit from but that doesn’t seem to
work as the assembly there doesn’t have a dependency set since the parent
doesn’t have any dependencies.

Is there a better way to go about this.  Using .dpkg is way easier in our
environment.

-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile




Re: Looking for a way to visualize dependency structure of my multi-module pom project

2015-04-12 Thread Laurence Bordowitz
I wanted to do this at one point. I just wrote a quick perl script to go 
through the XML of all my pom files, parse dependencies, and create an 
edge-list from module to dependency. You can use GraphViz, Gephi, Tulip, or 
some other visualizer to look at your dependencies.
Seriously, writing a quick parser utility for pom.xml files isn't so bad. It's 
xml. -- Larry Bordowitz
 


 On Saturday, April 11, 2015 10:34 PM, "Pisarev, Vitaliy" 
 wrote:
   

 Thanks Alejandro, what I meant is being able to plot the dependencies in a 
multi-module project. As far as I see- maven-graph-plugin generates a graph per 
module. Am I mistaken?


-Original Message-
From: Endo Alejandro [mailto:alejandro.e...@grassvalley.com] 
Sent: 08 April 2015 17:33
To: Maven Users List
Subject: RE: Looking for a way to visualize dependency structure of my 
multi-module pom project

If by module granularity you mean excluding/including certain modules, check 
this pull request I did on the maven-graph-plugin that has never been and 
probably will never be merged to the main line (Ah the beauty of opensource, 
you scratch your own itch and contribute it to the community but nobody cares). 
It does what I think you are asking for: it introduces a list of 
included/excluded groupIds.

https://github.com/fusesource/mvnplugins/pull/5

You would have to check it out and build it locally, but it worked fine last 
time I tried it over a year ago.

It currently does not allow filtering based on artifactId, but if you look at 
the diff, you can see that it would be fairly easy to introduce that change. 
For me, filtering by groupId was enough since I wanted to visualize only our 
group's dependencies

Hope it helps,

Alejandro

-Original Message-
From: Pisarev, Vitaliy [mailto:vitaliy.pisa...@hp.com]
Sent: Wednesday, April 8, 2015 04:46 AM
To: users@maven.apache.org
Subject: Looking for a way to visualize dependency structure of my multi-module 
pom project

I have a pretty large project (~30 modules) and want to visualize module inter 
dependencies, excluding 3rd party.

It seems that existing tools simply can't handle the maven reactor. The maven 
dependency plugin (dependency:tree goal) knows how to generate graphml, but 
only per module. And if I use the append flag, it simply shoves everything to a 
single file, so the output is a corrupted graphml.

I also found this 
tool but it seems 
that there is no way to control module granularity.

My last resort would be to parse the output of dependency:tree, but I thought 
I'll consult the community before this.


DISCLAIMER:
Privileged and/or Confidential information may be contained in this message. If 
you are not the addressee of this message, you may not copy, use or deliver 
this message to anyone. In such event, you should destroy the message and 
kindly notify the sender by reply e-mail. It is understood that opinions or 
conclusions that do not relate to the official business of the company are 
neither given nor endorsed by the company.
Thank You.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


  

Re: for maven-compiler-plugin

2015-04-12 Thread Lin Ma
Hi Dan,

Are there any message in your last reply? Looks like your message is
truncated. Thanks.

regards,
Lin

On Sat, Apr 11, 2015 at 11:34 PM, Dan Tran  wrote:

> looks like your pom reconfigures the default source ( ie
> build-->sourceDirectory)   this may help
> https://maven.apache.org/pom.html
>
> -D
>
> On Sat, Apr 11, 2015 at 11:10 PM, Lin Ma  wrote:
>
> > Thanks Dan,
> >
> > Followed your advice tried mvn -X compile and output is very verbose,
> which
> > items should I look at?
> >
> > I refer the document for compiler plug-in as well (
> > http://maven.apache.org/plugins/maven-javadoc-plugin/plugin-info.html),
> > and
> > not found it is mentioned where is source directory to search for for
> > compiler plug-in? Thanks.
> >
> > regards,
> > Lin
> >
> > On Sat, Apr 11, 2015 at 10:12 PM, Dan Tran  wrote:
> >
> > > try mvn -X compile, it will give you lots of hints too
> > >
> > > -D
> > >
> > > On Sat, Apr 11, 2015 at 10:11 PM, Dan Tran  wrote:
> > >
> > > > looks like your pom reconfigures the default source ( ie
> > > > build-->sourceDirectory)   this may help
> > > > https://maven.apache.org/pom.html
> > > >
> > > > -D
> > > >
> > > > On Sat, Apr 11, 2015 at 10:06 PM, Lin Ma  wrote:
> > > >
> > > >> Hi Dan,
> > > >>
> > > >> I have this question since I tried it compiles fine with sources in
> > > >> src/java/com/foo/..., are they default location as well? I do not
> find
> > > >> sub-directory "main" in the middle of the path.
> > > >>
> > > >> regards,
> > > >> Lin
> > > >>
> > > >> On Sat, Apr 11, 2015 at 9:59 PM, Dan Tran 
> wrote:
> > > >>
> > > >> > default main source is at src/main/java
> > > >> >
> > > >> > to add more sources, use build-helper-maven-plugin
> > > >> >
> > > >> > -Dan
> > > >> >
> > > >> > On Sat, Apr 11, 2015 at 8:10 PM, Lin Ma  wrote:
> > > >> >
> > > >> > > Hi Maven masters,
> > > >> > >
> > > >> > > For maven-compiler-plugin, how to check what are the source
> > > >> > > files/directories it will scan for to compile? And add other
> > source
> > > >> file
> > > >> > > directories? Thanks.
> > > >> > >
> > > >> > > thanks in advance,
> > > >> > > Lin
> > > >> > >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>