Oncofuse: Is there any way to avoid groovy-eclipse-compiler

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Oncofuse: Is there any way to avoid groovy-eclipse-compiler

Andreas Tille-5
Hi,

I'm trying to package oncofuse[1].  I used mh-make to create the
packaging skeleton.  I asked mh-make to ignore the dependency
groovy-eclipse-compiler since I was hoping that its not urgently needed
(and I do not have the slightest idea what this is and how hard it is to
package it as precondition).  Unfortunately I'm running into

   dh_auto_build
        /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/oncofuse-1.1.1 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/oncofuse-1.1.1/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/oncofuse-1.1.1/debian -Dmaven.repo.local=/build/oncofuse-1.1.1/debian/maven-repo package -DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...
[INFO]
[INFO] --------------------------< es.unav:oncofuse >--------------------------
[INFO] Building oncofuse 1.1.1
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ oncofuse ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ oncofuse ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.386 s
[INFO] Finished at: 2019-06-26T15:06:22Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project oncofuse: No such compiler 'groovy-eclipse-compiler'. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


Is there any way to use the Debian packaged groovy for this probably not
very complex project (only 7 *.groovy files) or is this groovy-eclipse
thingy providing something that can not be replaced?

Sorry for the naive question

      Andreas.


[1] https://salsa.debian.org/med-team/oncofuse

--
http://fam-tille.de

Reply | Threaded
Open this post in threaded view
|

Re: Oncofuse: Is there any way to avoid groovy-eclipse-compiler

Mykola Nikishov-2
Andreas Tille <[hidden email]> writes:

> I'm trying to package oncofuse[1].  I used mh-make to create the
> packaging skeleton.  I asked mh-make to ignore the dependency
> groovy-eclipse-compiler since I was hoping that its not urgently needed
> (and I do not have the slightest idea what this is and how hard it is to
> package it as precondition).  Unfortunately I'm running into

Do not ignore custom compiler ;-)

Seems the only option is to use Ant tasks directly [1] as GMaven is not
an option any more [2]:

> GMaven 2.x no longer supports any integration for compilation of
> Groovy sources. There were too many problems with stub-generation and
> hooking up compliation to the proper Maven lifecycle phases to
> effectivly support.

[1] https://groovy-lang.org/scripting-ant.html
[2] https://groovy.github.io/gmaven/

--
Mykola

Libre/Free Java Software Developer
https://manandbytes.gitlab.io/

Reply | Threaded
Open this post in threaded view
|

Re: Oncofuse: Is there any way to avoid groovy-eclipse-compiler

Thorsten Glaser-6
On Wed, 26 Jun 2019, Mykola Nikishov wrote:

> Seems the only option is to use Ant tasks directly [1] as GMaven is not
> an option any more [2]:

What about gmavenplus?

bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**********

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**********

Reply | Threaded
Open this post in threaded view
|

Re: Oncofuse: Is there any way to avoid groovy-eclipse-compiler

Andreas Tille-5
On Wed, Jun 26, 2019 at 10:03:03PM +0200, Thorsten Glaser wrote:
> On Wed, 26 Jun 2019, Mykola Nikishov wrote:
>
> > Seems the only option is to use Ant tasks directly [1] as GMaven is not
> > an option any more [2]:
>
> What about gmavenplus?

It seems you are refering to the package libgmavenplus-java.  What do I
need to do with this?

Similar question to Mykola who gave other hints:  Is there any example
that might turn your hint into some code?  I need to admit I have no
idea about all this groovy / maven stuff. :-(

Kind regards

       Andreas.

--
http://fam-tille.de

Reply | Threaded
Open this post in threaded view
|

Re: Oncofuse: Is there any way to avoid groovy-eclipse-compiler

Thorsten Glaser-6
On Wed, 26 Jun 2019, Andreas Tille wrote:

> It seems you are refering to the package libgmavenplus-java.  What do I
> need to do with this?

I’ve only seen it used here, I don’t speak Groovy, but it works
like this to compile test classes:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
[…]
        <properties>
[…]
                <!-- http://groovy.github.io/GMavenPlus/compileTests-mojo.html#targetBytecode -->
                <gmavenplus.javaRelease>1.8</gmavenplus.javaRelease>
                <!-- maven plugins -->
                <gmavenplus.plugin.version>1.7.1</gmavenplus.plugin.version>
        </properties>
[…]
        <build>
                <plugins>
                        <plugin>
                                <groupId>org.codehaus.gmavenplus</groupId>
                                <artifactId>gmavenplus-plugin</artifactId>
                                <version>${gmavenplus.plugin.version}</version>
                                <executions>
                                        <execution>
                                                <goals>
                                                        <goal>compileTests</goal>
                                                </goals>
                                        </execution>
                                </executions>
                                <configuration>
                                        <targetBytecode>${gmavenplus.javaRelease}</targetBytecode>
                                </configuration>
                        </plugin>
[…]

I assume the goal to compile main classes will differ;
duckduckgo for gmavenplus-plugin to get some semblance
of documentation.

Anything else would be trying it out until it works.
Sorry I cannot be more helpful :|

bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**********

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**********