On Tue, 2016-02-02 at 18:11 +0100, Emmanuel Bourg wrote:
> 2. Reuse groovy to package the next version of Groovy 2.x and then
> remove groovy2 (we keep the 2.x artifact to avoid updating all the
> reverse dependencies)
>
> 3. Turn groovy into a dummy package depending on groovy2. The groovy
> pack
On Mon, 2016-02-01 at 12:18 +0100, Andreas Tille wrote:
> I admit I have no idea how
> to
> craft the suggested publishedRule.
The maven.publishedRules usually gets generated with comments to help
you if you used mh_make. If not, check another project for reference
such as [1]. Adding the line be
On Mon, 2016-02-01 at 09:51 +0100, Andreas Tille wrote:
> Thanks for "reading aloud" for me - this might be due to my partial
> blindness for Java problems. :-)
No worries. Sometimes people overlook the simplest solutions because
they've been tackling a problem for too long.
>
> The next stumb
On Sat, 2016-01-30 at 18:05 +0100, Andreas Tille wrote:
> [ERROR] Failed to execute goal on project scala-maven-plugin: Could
> not resolve dependencies for project net.alchim31.maven:scala-maven-
> plugin:maven-plugin:3.2.2: Cannot access central
> (https://repo.maven.apache.org/maven2) in offline
On Thu, 2016-01-28 at 16:26 +0100, Andreas Tille wrote:
> As far as I understand its renamed by the same author.
You're right. I didn't realize this.
> I perfectly agree - but I have no idea how to find the according
> source
> code. I feel a bit unsafe to checkout the new repository and
> chec
On Wed, 2016-01-27 at 15:08 +0100, Andreas Tille wrote:
> Reading "compile" and "link" would tell me
> that these are not needed only for testing, right?
Don't confused with . Goals are named subroutines from
the plugin. Phases are standard Maven names. If you prefer, goals tell
Maven what to use
On Wed, 2016-01-06 at 20:19 +0100, Felix Natter wrote:
> > $ dpkg -L libflamingo-java | sort
> > /.
> > /flamingo
> > /flamingo/build
> > /flamingo/build/libs
> > /flamingo/build/libs/flamingo-7.3-javadoc.jar
> > /flamingo/build/libs/flamingo-7.3-sources.jar
> > /usr
> > [...]
Installing this deb
Hey Felix,
On Sun, 2015-12-27 at 19:59 +0100, Felix Natter wrote:
> (adapted from
> http://anonscm.debian.org/cgit/debian-med/picard-
> tools.git/tree/debian/rules)
> installs the poms correctly, but not the jars (probably since it
> doesn't
> know where they are ;-)).
This project uses the javah
On Wed, 2015-12-02 at 09:58 +0100, Emmanuel Bourg wrote:
> > I think this comes back to our conversation about Maven 3 searching
> > for
> > that metadata file unless a version is explicit specified.
>
> So if I understand well:
>
> 1. the plugin defines the sequence of goals executed for each ph
On Fri, 2015-11-27 at 10:52 +0100, Emmanuel Bourg wrote:
> Curiously the pom.xml doesn't reference the install
> plugin at all. If I change the Maven packaging from bundle to jar it
> builds fine. So there is a weird interaction with the bundle plugin.
The bundle type provided by the maven-bundle-
On Fri, 2015-11-13 at 16:40 +0100, Emmanuel Bourg wrote:
> I've eventually merged your changes [1] and uploaded maven-debian
> -helper
> 2.0 to experimental.
Awesome! Good to hear we are finally moving on from Maven 2.
> I encountered some issues with the bootstrapping
> and I had to revert back
Classloader issues are always a pain to diagnose. I wrote up a small
test program and it appears to work on this machine, but then I found
this little tidbit in the oracle docs [1].
Class-Path: The value of this attribute specifies the relative URLs of
the extensions or libraries that this applica
On Tue, 2015-04-07 at 22:45 -0300, Rogério Brito wrote:
> * Would you be willing to answer some stupid questions and teach me
> the
> basics so that I can work on theses packages (and, possibly, other
> dependencies), as long as it helps the packaging of Java for Debian?
Here's something to st
I added another commit on the maven3 branch that will generate plugin
and group metadata when copying the repo. It will ignore any existing
metadata, i.e. the bits you added to maven-javadoc-plugin. We should now
be able to rebuild maven-debian-helper package and test it against all
packages that u
On Tue, 2015-03-17 at 11:10 +0100, Emmanuel Bourg wrote:
>
> Great, let me know when it's ready to be merged.
All ready [1] and works on two packages that I tried. Would you prefer a
github pull request? I've included 2 commits (the last two) which aren't
strictly necessary, but fix the bug that
On Mon, 2015-03-16 at 17:58 +0100, Emmanuel Bourg wrote:
> > A quick look at deb-triggers looks like it's just what we need. I'll
> > investigate a solution similar to the triggers in man-db.
>
> Ideally a trigger that doesn't use Java would be necessary, since the
> Java libraries do not depend o
On Sat, 2015-03-14 at 09:03 +0100, Emmanuel Bourg wrote:
> You mean that a plugin can't be invoked from the command line if the
> metadata file is missing, right? In this case I think we can live with
> it. We don't execute many plugins when a package is built, the javadoc
> plugin is probably the
On Mon, Mar 9, 2015 at 7:05 AM, Miguel Landaeta wrote:
>> Ideally we should switch maven-debian-helper to Maven 3 as soon as
>> possible after the end of the freeze, this will leaves us a full
>> development cycle to complete the transition to Maven 3. I don't
>> remember what was missing to compl
> > com.github.spullara.mustache.java:compiler is a bundle. Inform mh_make
> > that dependencies of type jar which may match this library should be
> > transformed into bundles automatically?
>
> I don't really understand the question. Experimentation shows that
> answering "yes" adds a line
>
>
The metadata might also be used to obsolete some of the
maven-repo-helper logic. What do you guys think?
Cheers,
Andrew
On Sat, 2014-09-06 at 15:40 -0700, Andrew Schurman wrote:
> On Sat, 2014-09-06 at 10:51 +0200, Emmanuel Bourg wrote:
> > Hi Andrew,
> >
> > Thank you f
On Sat, 2014-09-06 at 10:51 +0200, Emmanuel Bourg wrote:
> Hi Andrew,
>
> Thank you for tackling this issue.
>
> Le 06/09/2014 06:53, Andrew Schurman a écrit :
>
> > I've been taking a look at what it would take to update the
> > maven-debian-helper package to
Hey guys,
I've been taking a look at what it would take to update the
maven-debian-helper package to use maven 3 [0]. This includes all the
changes that I made manually to test that maven 3 could work with some
packages with minimal changes as well as a few extras. I've used the
assumption that ma
I hacked the maven-debian-helper scripts to see if they would work
with maven3. I've tried it with one of the packages that I've created
(libweupnp-java) and it appears to almost work while only changing the
maven version. Everything ran fine except the javadoc generation
(likely something I missed
Although a flat file repo would be sufficient, I believe setting up
something like nexus would be more beneficial. It's relatively straight
forward. They provide an open source version that can be used.
My work doesn't currently work with remote repos, but It should be a simple
change.
Cheers,
A
Hey guys,
Last week was all about testing and hardening the plugin so that I had
confidence of the functionality of the areas I explored. It was quite a
useful exercise as well as I found quite a few bugs that I didn't see on my
first walkthrough. For the few minor issues left, I intend to fix in
I'm no expert of debian package builds, but from a maven standpoint, it
sounds like a missing plugin. Have you tried adding
libbuild-helper-maven-plugin-java to build depends? If it was a maven 3
incompatibility, you'd see a much different error and probably a failed
build on your local machine.
C
Hey guys,
This week I my mission was to try and build projects with no formal
source control. Sometimes these projects may have uploaded an
additional sources classified artifact with their main artifact in
order to help debug the project. In most cases, simply compiling these
sources would create
Hey guys,
I missed my update last week so here is one for the past two weeks. I
had an Ant builder which started to deal with more complex projects.
Complex in this case consisted of projects with had jars or classes in
them. These were removed and replaced with ones which were built
locally. In o
Hey guys,
This week my goal was to finish Ant support and it is almost complete.
I got to test it out on a few different ant projects taking into
consideration the different ways that they could be build. Suffice to
say, this was where most of my effort was spent because there are no
standards for
Hey Adam,
Like javascript, there are a few package managers for Java. Maven is
one of the dominant ones. It acts like npm and grunt/gulp for
javascript. It should handle setting up all the command line options
for compiling, but if you are going to run something manually, you'll
still need those m
Hey guys,
This week I was hoping to finish up ant support. Unfortunately, I got
a quite busy during the week and didn't have too much time to work on
it. To get a better understanding of the needs of ant projects, I
tried my hand at packaging one: jain-sip. It got put on hold due to
licensing, but
Hey guys,
What kind of artifacts would Java projects consider non-free? More
specifically, what are examples of some of the things that you would
remove from an orig.tar which would be inappropriate for a deb package
because of licensing, etc? I know jars are one example, but are there
others? Fai
Hey guys,
This week I got to some bug fixes and continued looking into support
for Ant based projects. It was fairly easy to add with the
infrastructure I had using the maven-antrun-plugin as an example. When
looking at some real Ant projects, I found they could potentially have
jars committed in
Hey guys,
I'll keep this weeks update short.
I'm happy to report that the plugin that I've been developing now
works end to end subject to a few conditions. Projects must be in in
your local repo (from central or some other maven repo), built with
Maven and have an accessible SCM url (from its Ma
Hey guys,
Over the past week I've been able to weave all the code I have
together so that it looks like a maven plugin. There wasn't too much
weaving to really. My time has been mostly testing the plugin to find
edge cases in the logic that's already implemented and there were
quite few. For examp
Hey guy,
Last week I started to build Maven projects from source repositories
using a forked maven process. Repositories were identified from maven
metadata. It had quite a lot of assumptions and still pulled
dependencies from central.
This week on the other hand was quite busy: I stared to fill
Hey Emmanuel,
I suppose that is partly my fault. I've been trying to tackle the low
hanging fruit first which when put together will become the project.
My emails are probably a little lower level than they should be. And I
don't think I've done a good job describing the why or inputs and
outputs
On Monday, June 9, 2014, Daniel Pocock wrote:
>
>
> On 09/06/14 11:16, Andrew Schurman wrote:
>> On Sat, Jun 7, 2014 at 1:08 AM, Daniel Pocock
wrote:
>>>
>>>
>>> On 07/06/14 09:33, Andrew Schurman wrote:
>
>>>
>>> For some
On Mon, Jun 9, 2014 at 3:54 AM, Matthew Vernon wrote:
> Daniel Pocock writes:
>
>> On 07/06/14 09:33, Andrew Schurman wrote:
>> > I recall reading that packaging a maven project for debian requires
>> > maven to be in offline mode during the build. I can try t
On Sat, Jun 7, 2014 at 1:08 AM, Daniel Pocock wrote:
>
>
> On 07/06/14 09:33, Andrew Schurman wrote:
>> Hey guys,
>>
>> Last week I was able to fetch source of artifacts which has an
>> tag in their maven metadata. By leveraging the maven-scm-plugin, I was
>&g
Hey guys,
Last week I was able to fetch source of artifacts which has an
tag in their maven metadata. By leveraging the maven-scm-plugin, I was
able to get the vast support of VCSs for free. It also provides a well
documented interface for extension in case other VCSs come out or
someone is using
H
This week, I started implementation on the SCM builder portion of the
project. It is being built as a plexus component for easy addition
into the Maven world. So far, I've figured out how to get the SCM
information from an arbitrary maven artifact and can checkout the
source code. Source code is
Hello Folks,
This is my first official report for the Google Summer of Code about my
project on recursively building dependencies of java projects. More details
can be found on my project proposal page [1]. For those unaware, you can
expect to hear from me once a week throughout the summer detaili
Greeting fellow Java hackers,
It's that time of year again when students ease up on their studies and
help contribute to the open source community through the Google Summer of
Code. I've been selected this year to build project which could be used to
help build a java projects dependencies (and th
44 matches
Mail list logo
