What I'm missing is just a guide how to contribute the code to Apache
NetBeans, and I would do it myself. But maybe it is there and I just don't
know.
Matthias Bläsing schrieb am Do., 28. Mai 2020,
20:48:
> Hi,
>
> Am Donnerstag, den 28.05.2020, 14:44 -0400 schrieb Scott Palmer:
> > IANAL, but
Thx to all, I will create a ticket at Bennos repo, will share it here and the
rest I will read what is still missing then.
Cheers
Chris
Gesendet von Mail für Windows 10
Von: Geertjan Wielenga
Gesendet: Freitag, 29. Mai 2020 09:16
An: dev@netbeans.apache.org
Betreff: Re: Contributing
On Fri, 29 May 2020 at 07:51, Mario Schroeder wrote:
> What I'm missing is just a guide how to contribute the code to Apache
> NetBeans, and I would do it myself. But maybe it is there and I just don't
> know.
Funnily enough, you can't "contribute" it unless you wrote it. All
this needs is a
NetBeans is an Apache project, like any other Apache project. Take a look
at apache.org for info or at netbeans.apache.org for anything specific to
NetBeans.
Gj
On Fri, 29 May 2020 at 08:51, Mario Schroeder
wrote:
> What I'm missing is just a guide how to contribute the code to Apache
>
Was just reading this myself. Seems to be specific to managed
Ant-based projects, not (say) Maven or Gradle or freeform Ant. As far
as I can tell, NetBeans itself is not at fault, this is just a virus
that infects a type of build system, pretty much all of which presume
that the build is running
What's all this, then?
https://securitylab.github.com/research/octopus-scanner-malware-open-source-supply-chain
--
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."
-
To
A further note:
> the malware also infected any JAR files that were available in the project,
> such as dependencies—not necessarily just build artifacts
If I understand correctly what is being said here, this kind of attack
only makes sense for a build system which keeps binary dependencies in
Hi,
for PP3 we need to parse OSGI JAR and NBM files. For NBMs this is easy
because you only need to extract the info.xml file and parse that.
For OSGI JARs this is harder. Two new parsers would be needed: A
MANIFEST.MF parser and a properties file parser. This can be done in
PHP but it is a PITA
On Fri, 29 May 2020 at 19:11, Matthias Bläsing
wrote:
> It also feels nuts as our primary language has perfectly working
> parsers and so I'd like to implement the parser converter in java.
>
Well, it's got OpenJDK 8 on it.
Best wishes,
Neil
